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

With no annotations provided, the description carries the disclosure burden. It reveals meaningful behavioral traits: no LLM cost, pure state transition, cancellation request semantics, and cascade to descendant subagents. It does not describe result/return behavior, but the disclosed details go well beyond the tool name.

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 reasonably sized but not perfectly front-loaded. The actual purpose 'Stop a running agent' appears in the third sentence after the introductory 'Aurora agent surface' context. It is compact, but some early sentences are contextual rather than action-oriented.

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 simple one-parameter tool with no output schema, the description covers the purpose, preconditions (active state), and side effects (cascade). It does not mention error cases or exact response shape, but the essential context for calling it correctly is present.

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 100%, so the schema already fully documents agentId as 'MongoDB agent _id to stop.' The description adds no additional parameter-level detail, which is acceptable given the complete schema coverage.

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 clearly states the verb and resource: 'Stop a running agent.' It adds specific behavioral detail—sends a cancellation request and cascades to all descendant subagents—which distinguishes it from siblings like archive_agent or reject_agent_action.

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?

It provides clear context for when the tool is relevant: when actively managing an Aurora agent and when the agent is in an active state. However, it does not explicitly mention alternatives or when not to use this tool versus related sibling tools.

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