Two tools with explicit schemas, descriptions, and tool annotations. Both tools have well-structured input/output schemas using Zod with proper type definitions and parameter descriptions. Tool names are action-oriented (create, docs_context). Descriptions are substantive (100-200 chars). However, parameter descriptions contain template variables (${FLOW_STACKS}, ${DEFAULT_STACK}) that are not expanded in the visible code, reducing clarity for LLMs. Output schemas are documented. Error handling is basic, no recovery guidance or actionable error messages visible in the tool implementations.

• Expand all template variables in parameter descriptions at registration time. Replace ${FLOW_STACKS} with actual enum values like 'react | vue | angular | svelte' so LLMs see concrete options.
• Add recovery guidance to error responses. Example: 'Invalid stack: got "xyz". Valid stacks are: react, vue, angular. Call create with stack=react to proceed.'
• Document the default behavior for optional parameters. For create's 'stack' parameter, clarify: 'If omitted, the tool will prompt for stack selection (requiresStackSelection=true in response).'
• Add query format guidance to docs_context. Example: 'Queries should be specific API names or feature keywords (e.g., "useState", "useEffect", "hooks"). Vague queries like "how to" may return low-relevance results.'
• Implement cursor-based pagination for docs_context results. Add a 'nextCursor' field to the response and accept an optional 'cursor' parameter to enable iteration through large result sets.

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry