search_package_docs

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

Describes discovery sources, result selection (highest-scoring pages), and bounding constraints. No annotations provided, so description carries the full burden; it adequately discloses non-destructive read behavior.

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?

Four sentences, front-loaded with purpose, zero wasted words. Efficiently covers purpose, sources, return format, and constraints.

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 no output schema and complete parameter descriptions, description covers what the tool does, sources it uses, and result bounding. Lacks explicit return structure but sufficient for selection and invocation.

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% with clear descriptions for all 4 parameters. Description does not add additional detail beyond schema, so baseline of 3 is appropriate.

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?

Clearly states action (search), resource (package documentation), and scope (discovers pages from specific sources). Differentiates from sibling tools like get_package_docs and get_package_info by focusing on search and bounded results.

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?

Implies usage for searching documentation but lacks explicit when-to-use or when-not-to-use compared to siblings like get_package_docs. No guidance on alternatives or prerequisites.

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