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

Annotations already establish readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond those hints: the tool returns evidence and citations, produces a grounded answer only when the private resolver is enabled, and warns that excerpts alone are not a complete ruling. These are genuine, non-redundant disclosures.

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?

The description is compact and front-loaded with the core purpose. Each sentence contributes meaning: purpose, return behavior, caveat, and a clarifying non-feature. The final 'No package download' sentence is slightly tangential but short and relevant to setting expectations. No filler or redundancy.

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?

For a simple search tool with no output schema, the description covers the key operational facts: resource scope, return content, conditional grounded-answer behavior, and an important epistemic caveat. It does not fully compensate for the low schema coverage on parameters, but the schema's named parameters and enum are largely self-explanatory and annotations cover the safety profile. The definition is adequate and near-complete.

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 description coverage is 0%, so the description needed to explain the query and language parameters, but it does not mention either by name or give usage guidance. The word 'Search' loosely implies query is the search text, and the schema's enum/default covers language, but the description itself adds no parameter-level meaning. The language parameter also remains underserved, especially given the mention of 'English evidence.'

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 opens with a specific verb and resource: 'Search the validated USA Pickleball rulebook.' It also states what the tool returns (evidence, citations, grounded answer), which distinguishes it from the sibling MYOPL search tools and player-rating tool. The purpose is immediately clear and not interchangeable with any sibling.

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?

The description gives implied context: use it to search the USA Pickleball rulebook. It also offers practical guidance about preserving clarification requests and not treating excerpts as complete rulings. However, it never explicitly contrasts with alternatives like search_myopl_help or search_myopl_website, so an agent must infer the boundary between those tools.

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