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

With no annotations present, the description carries the full behavioral burden and does so well: it states the tool always returns a denial, cites the incident and the reason (no authenticated ownership check), explains what the summary used to expose, and says all arguments are ignored. That is exactly the context an agent needs to avoid a wasted or misleading call.

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 operational content is front-loaded well enough, but the body spends several sentences on incident narrative ('incident VM-IR-2026-07-28-COORD-01', what the summary used to expose, 'closed to every caller while owner-scoped access control is rebuilt') that partially restates the same point three times. Trimming the incident detail to one clause would preserve all decision-relevant meaning.

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?

An output schema exists and needn't be explained, and the description covers the one thing that matters for a disabled stub: it always denies. Combined with the argument-ignored note, an agent has everything needed. Only the absence of a suggested working alternative leaves a small gap.

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 0% for the single pioneer_key parameter, so the description must compensate — and it does by declaring 'all arguments are accepted for schema stability and are ignored', which fully defines the parameter's effective semantics (none). It does not explain what pioneer_key would normally mean, which is a minor residual gap.

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 first sentence names a specific verb and resource (return current team coordination state and session summary), which distinguishes it from the handoff siblings that create/read specific handoffs. It does not explicitly contrast itself against any sibling, which keeps it at 4 rather than 5.

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 description gives an unambiguous when-NOT: 'TEMPORARILY DISABLED', 'always returns a denial', 'closed to every caller'. An agent reading this knows not to depend on it. It stops short of naming a working alternative among the siblings (e.g. coordination_handoff_read), which would be needed for a 5.

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