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

Annotations already establish a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds real behavioral context beyond them: the default crisis set is not ranked by likelihood, optional fields are inferred and reported back, and compliance entries are surfaced in the notification steps.

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?

Four sentences, front-loaded with the return value, then the optional-input behavior. The 'Name the crises you know of to get those playbooks' phrasing is slightly conversational but earns its place by conveying the optional-input contract.

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?

No output schema exists, and the description covers what comes back (playbooks with team and notification steps) plus defaults for the two most behaviorally significant optional params. That is enough for a read-only 9-param tool, with only minor gaps around how unlisted crises/inputs are validated.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema doesn't: it explains the fallback for potential_crises and that compliance_requirements are consumed by the notification steps. It also frames the four required inputs as the core driver of the playbook, though the industry vs your_sector distinction is left to the schema.

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 and resource ('returns crisis playbooks with a response team and notification steps for each crisis') and names the inputs that drive it. The output is concrete enough that an agent can distinguish it from the unrelated siblings (competitive_intel, retention_playbook, etc.) without opening any schema.

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?

Gives conditional guidance for the optional fields: name crises to get those playbooks, or omit them and the tool falls back to a sector default set; compliance items feed the notification steps. It doesn't state when to prefer another tool, but the sibling set is a different domain, so no exclusion is genuinely needed.

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