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

Beyond the readOnly and closed-world annotations, the description discloses meaningful behavior: calm words narrow to quiet/editorial/sharp families, history blocks recent directions/heroes/effects, the group check blocks two-of-three matches, and the name number breaks ties. It still omits what the tool returns or how errors are surfaced.

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, but it is not front-loaded: it opens with rule numbers and a dense semicolon chain rather than a plain statement of the operation. The content is relevant, but the structure makes the agent parse jargon before understanding the action.

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 rule-based selection tool with five parameters and no output schema, the description should explain the return value and clarify the referenced rules. Instead it assumes external knowledge of rules 1-5 and never says what the tool produces after applying them.

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 80%, so the baseline is 3. The description adds useful meaning for `calm`, `history`, `product`, and `fitting`, but it never explains the required `recipe` parameter, leaving a critical gap.

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 names a specific operation: applying rules 3-5 and recent-picks/group checks to narrow and choose directions, with the agent judging which directions fit the subject. This is more specific than a tautology, but it does not clearly distinguish the tool from related siblings such as check_pick or get_family.

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?

There is implied workflow guidance: the agent is told to judge fitting directions under rules 1, 2, and 4 and pass them as `fitting`. However, it never states when to use this tool versus alternatives, nor does it name exclusions or sibling tools.

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