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

With no annotations, the description carries the full burden and does substantial work: it discloses that the action is a state transition, marks the latest assistant message as errored, traces the rejection, and publishes a websocket update. It does not mention whether the operation is reversible or what permissions are required, but the core behavior is well covered.

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 compact and information-dense. Every sentence earns its place: the first frames scope and cost, the second gives the usage precondition, and the third lists concrete behavioral effects. No filler or repetition.

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 one-parameter tool with no output schema and no annotations, the description covers the action, valid states, and side effects quite well. It does not explicitly state what the tool returns after rejection, which would be useful with no output schema, but the low complexity and rich effect description make this a minor 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 100% and the single parameter agentId is already described as 'MongoDB agent _id to reject.' The description adds the endpoint pattern POST /api/agent/:agentId/reject, which reinforces that agentId is a path identifier, but it does not materially expand on schema semantics. 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?

The description states a specific verb and resource: 'Reject a semi-automated agent that is waiting in pending_plan_approval or pending_action_approval.' It also distinguishes itself from sibling tools by scoping to the Aurora agent surface and to pending-approval states, making it clear this is the rejection counterpart to approval or stopping 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?

It provides explicit when-to-use guidance: 'Only relevant when actively managing an Aurora agent' and specifies the exact pending states required. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5, but the conditionality is clear enough for an agent to route correctly.

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