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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well-covered. The description adds only that it returns 'matching jokes with IDs and text,' which is a minor behavioral detail. It does not disclose any additional constraints (e.g., pagination, ordering, or filtering nuances) beyond what annotations and the schema already provide.

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 two short sentences, each earning its place: the first states the action, the second states the output. There is no redundant information or filler. It is efficiently front-loaded and easy to scan.

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, the description is complete. The output schema exists, so return values are documented elsewhere. Annotations cover the operational safety (read-only, idempotent). The tool has only two parameters, both self-explanatory via the schema. No additional context (e.g., authentication, rate limits) is needed for this straightforward read operation.

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?

The schema has 100% parameter description coverage: both 'query' and 'limit' are described. The description's phrase 'by keyword or topic' essentially rephrases the 'query' parameter without adding new meaning. Since the schema carries the full semantic weight, the baseline score 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?

The description clearly states the tool's function: 'Search dad jokes by keyword or topic.' The verb 'search' combined with the resource 'dad jokes' is specific, and the output of 'matching jokes with IDs and text' clarifies what is returned. This implicitly distinguishes it from sibling tools like 'get_joke' (retrieve a specific joke) and 'random_joke' (get a random joke), making the purpose unambiguous.

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 clearly conveys the tool's context: use it to find jokes based on a keyword or topic. However, it does not explicitly mention alternatives or exclusions (e.g., 'for a specific joke, use get_joke'). The verb 'search' provides enough contextual cue for when to use this tool, but without explicit sibling differentiation, it stops short of a 5.

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