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 the matching-then-fallback behavior, which is genuinely useful context. But it says nothing about what a match produces, confidence, or behavior when no scenario matches, so it adds only moderate value beyond annotations.

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, tightly worded sentence with no filler, and the core action ('match a user request') is front-loaded ahead of the fallback caveat.

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 no output schema, the description bears more of the burden for return behavior, yet it does not say what a successful match yields (a scenario name? a manifest?) or what happens on no match beyond 'falling back.' For a selection/routing tool this leaves a meaningful gap, though it is otherwise adequate.

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 is documented with a concrete example in the schema itself. The description adds no extra meaning beyond what the schema provides, so the 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?

States a specific verb + resource: 'Match a user request to a known scenario pattern.' The added clause 'before falling back to generic playbooks' hints at its relationship to the playbook siblings, though it never names tide_choose_playbook or tide_list_scenarios, so sibling differentiation is only partial.

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 'before falling back to generic playbooks' implies an ordering decision (try this first, use playbooks if no match), which is useful implied usage. However, it gives no explicit condition for what constitutes a match, when to abandon the search, or which sibling to call instead, leaving the agent to infer.

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