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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the recommendation is deterministic, single-result vs ranked list, or based on what matching logic, which is the key behavioral question for a recommender.

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?

A single short sentence with the core purpose front-loaded and no filler. It is efficient, though efficiency here partly reflects under-specification rather than tight editing.

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?

With one fully documented parameter and annotations covering safety, the minimum is met. But with no output schema, the description should state what comes back (a playbook identifier? name? rationale?) and how it differs from tide_playbook, which it leaves entirely unexplained.

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 100% and the single `situation` parameter even carries an example ("add login to a new Next.js app"), so the schema carries the burden. The description adds nothing about how detailed or free-form the situation string should be, so baseline 3 applies.

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?

"Recommend the right playbook for a given situation" names the resource (playbook) and the action (recommend), but it largely restates the tool name and gives no criteria for what "right" means. It also fails to distinguish it from siblings like tide_playbook, tide_choose_scenario, and tide_list_scenarios, so an agent cannot tell which selector to call.

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 phrase "for a given situation" weakly implies usage, but there is no explicit when-to-use, no exclusions, and no mention of when to prefer tide_playbook or tide_choose_scenario instead. Given three overlapping sibling tools, this omission is a real routing risk.

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