Find words by pattern

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond annotations by stating that matches include list, grade range, and page, and that matching is case-insensitive. It omits pagination/limit behavior, which keeps it below 5.

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 tight sentences, front-loaded with the core purpose and followed by return and case-sensitivity details. Every sentence carries useful information with no repetition or filler.

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 six-parameter search tool with no output schema, the description does a reasonable job explaining pattern matching and return fields. However, it leaves out limit/pagination behavior, language filtering, and whether multiple pattern filters are combined with AND or OR, so an agent would still need to inspect the schema and infer behavior.

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 only 33%, so the description needs to compensate. It usefully explains the semantics of the starts_with, ends_with, and contains pattern parameters with examples and notes case-insensitivity, but it does not clarify how those parameters combine, nor does it explain language filtering or limit behavior.

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 states a specific verb and resource: finding words in lists by letter pattern, with starts-with, ends-with, and contains modes. The pattern-focused purpose clearly distinguishes it from sibling tools like get_words_for_grade and get_word_list.

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 implies this is the tool to use for pattern-based word lookup, but it does not explicitly say when to choose it over siblings such as get_words_for_grade or get_word_list. No exclusions or alternative-routing guidance are provided.

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