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

With no annotations provided, the description carries the full disclosure burden and does so thoroughly. It reveals the temporary disablement, the security incident reference, that all arguments are ignored, and the exact error returned. This is exemplary transparency about actual runtime behavior.

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 well-structured: status, disablement notice, rationale, and return behavior are clearly separated and front-loaded. It is somewhat longer than strictly necessary because it includes background on the security vulnerability, but every section serves a transparency purpose and there is no redundant filler.

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 disabled tool with one ignored parameter, the description is complete: it explains what the tool was for, why it is disabled, that every call will fail, that arguments are ignored, and what error an agent can expect. Nothing needed to safely invoke or avoid invoking this tool is missing.

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% and the only parameter, pioneer_key, has no schema description. The description fully compensates by stating that 'All arguments are accepted for schema stability and are ignored,' which tells the agent the parameter value is irrelevant and need not be researched or specified.

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 opens with a specific verb+resource: 'Return current team coordination state and session summary.' It then immediately clarifies the actual current behavior (always returns a denial), so an agent knows exactly what the tool does both nominally and operationally, and can distinguish it from sibling handoff/consult tools.

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 explicitly states when NOT to use the tool: it is 'closed to every caller' and 'always returns a denial,' giving unambiguous usage guidance. It does not name an alternative tool to use instead, but for a disabled tool this exclusion is the critical guidance; no alternative is required.

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