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

Annotations already declare this is a non-read-only, non-idempotent write, and the description adds useful lifecycle context: the request is recorded, surfaced on team optics, and the reply returns to the inbox. However it does not explain why the operation is marked destructive or what signing as agent_id implies about attribution, so it adds only moderate value beyond the 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?

Short and front-loaded, leading with the gating condition before the mechanics. The all-caps fragments and bracketed emphasis are a bit stylized but do not add bloat.

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 4-parameter write tool with no output schema, the description covers the trigger, the workflow, where the record goes, and where the reply lands. Only team_id's role and the destructive flag's meaning are left 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 coverage is 50%, and the description partly compensates by clarifying that agent_id is the signing identity ('the escalation is raised AS agent_id') and by echoing the intent of question and context. team_id is never mentioned, leaving one gap that neither schema nor description fills.

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 target ('Flag the human') plus the triggering condition, and clearly distinguishes itself from siblings like list_escalations and resolve_escalation by describing the act of raising, not reading or closing, an escalation.

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 an explicit when-not gate ('ONLY when the team cannot solve a blocker alone') and an alternative ('Try teammates first'), which is strong context. It stops short of naming the specific sibling to use instead (e.g. advise_team), so routing is left slightly to inference.

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