prd_search

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description must supply behavioral context. It explains the search is semantic and accepts natural language, but does not disclose read-only behavior, result format, or potential delays. Adequate for a simple search tool, but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences that immediately convey purpose and query capabilities. No extraneous information; front-loaded for quick agent scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (3 params, no output schema), the description covers core functionality well. However, it omits details about the result format (e.g., list of PRD IDs or full text) and does not mention pagination behavior beyond the limit parameter. Minor gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (all parameters described). The description adds context about searching across all saved PRDs and natural language queries, but does not significantly enhance parameter understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool performs 'Semantic search across all saved PRDs' and specifies searchable criteria (topic, service name, feature description, natural language). It distinguishes from sibling tools like prd_check_api_refs or prd_validate, and even from other search tools (skill_search) by explicitly targeting PRDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like skill_search or other PRD tools. The description does not mention prerequisites, limitations, or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.