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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description usefully adds that operators are read-only and that resume/delete are approval-gated, which annotations cannot express. However, for a destructive 13-parameter mutation it says nothing about blast radius (what deleting an agent destroys, whether pause is reversible), workspace scoping, or the mandatory idempotency_key's effect on retries.

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?

Two compact sentences with no filler and the capability statement front-loaded. Efficient, though the extreme brevity is partly the cause of the parameter gaps rather than deliberate restraint.

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?

Given ten optional nested parameters, zero schema descriptions and no output schema, the definition is under-informative: an agent cannot know how to populate dry_run, template, capabilities or connected_accounts from this text. It does cover the safety-critical facts (destructive, approval-gated), which keeps it above inadequate.

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 description coverage is 0%, so the description carries the full burden and it barely compensates: only the `action` values are implied. Key parameters like idempotency_key, dry_run, template, capabilities, connected_accounts and instructions go entirely unexplained in both the schema and the description.

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?

Names a specific resource ('teammates') and enumerates the exact operations (create, edit, pause, resume, delete), which map cleanly onto the `action` enum. An agent can distinguish it from agents_list or agent_runs_start without opening the schema. Minor gap: 'edit' vs the schema's 'update', and no explicit routing note to agents_list.

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 second clause gives real usage constraints: read-only operators cannot use it, and resume/delete require approval. That tells the agent when the call will be blocked, but it never names an alternative tool or states when to prefer agents_list/templates over this.

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