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

With no annotations to lean on, the description still carries real behavioral weight: it discloses the auth requirement (signed-in session) and two concrete side effects — the call is canceled and its reserved budget is released. It omits reversibility, idempotency, and error behavior, keeping it below a 5.

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 tight sentences with the scoping/auth constraint front-loaded, followed immediately by the action and its consequences. Every clause earns its place; nothing is padded.

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 two-param mutation with no annotations and no output schema, the description covers the auth gate and the operation's effects adequately, but leaves the parameter meanings and the result of a decline undeclared. It is minimally sufficient rather than complete.

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% for both required parameters (id, workspaceId), so the description must compensate and does not. It never explains what 'id' identifies versus 'workspaceId', nor the expected UUID formats, leaving both params semantically opaque.

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 verb ('decline') and resource ('a call an AI assistant asked for'), which cleanly separates it from calls_approve and calls_cancel by describing the approval-workflow context. It does not name any sibling explicitly, so it stops short of a 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 phrase 'Signed-in session only' establishes an auth prerequisite, and the framing implies this is the rejection half of an assistant-requested-call approval flow. It never states when-not to use it or points to calls_approve/calls_cancel as alternatives, so guidance is implied rather than explicit.

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