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

With no annotations, the description carries the full behavioral burden. It discloses that the tool provides tiered SOPs, scenario copy, a 30-minute red-alert response, and reputation repair guidance, but it does not explain whether it generates content, retrieves templates, or what kind of response or brief is returned.

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 a single front-loaded sentence with no filler. The parenthetical scenario list is useful, though the sentence is dense and packs multiple clauses together rather than separating the tool's core function from its crisis stages.

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?

The description names the relevant crisis categories and response stages, which helps an agent understand the domain. But with no annotations and no output schema, it leaves key invocation details unclear, such as how the query should describe an incident and whether the result is a playbook, copy templates, or a structured brief.

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 single optional query parameter is already documented in the schema. The description does not add syntax, scoping behavior, or examples beyond the schema's statement that the query scopes the brief, so the baseline score is appropriate.

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 identifies a specific domain and resource: a tiered crisis-response SOP and scenario copy library covering food-safety, service, franchise, endorsement, and backlash situations. It is clear what the tool provides, though it lacks an explicit action verb and does not name a sibling alternative for differentiation.

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?

Usage is implied through phrases like 'red alert' and 'post-crisis reputation repair,' which signal crisis and recovery contexts. However, it gives no explicit when-to-use guidance versus related tools such as brand-mention-repair or review-rescue-agent, and no exclusions or prerequisites are stated.

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