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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description doesn't need to restate that. It does add real context beyond the annotations – attribution ('credited to the person this connection acts for') and the note cap – but omits whether flagging is idempotent, whether teammates are notified, and what happens if the chat is already flagged.

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 front-loaded sentence that puts the state change first, then the optional parameter detail, then attribution. Nothing is redundant or padded.

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 low-risk mutation with no output schema and clear annotations, this is close to sufficient, but it never says what a successful flag returns or how already-flagged, unknown-contact, or invalid-brand cases behave – details an agent needs to handle failures.

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 67% and it already documents contact (source keys) and brand (slug from get_overview). The description's addition is the note being optional and capped at 500 characters, but the note field itself has no schema description, so the gap is only partly closed. Baseline 3 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?

States a specific verb (Flag) and resource (a chat) plus the concrete outcome: it waits for the team under Needs you. An agent can distinguish this triage/handoff action from the read-side sibling list_needs_you without opening either 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?

Usage is implied by 'waits for the team' – escalate a chat to human/team attention – but the description never says when to prefer this over closing, replying, or simply reading the chat, and offers no exclusions or prerequisites.

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