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

Annotations already declare the mutation profile (readOnlyHint=false, idempotent=false, destructive=false, openWorld=false), so the bar is lower. The description does add genuine behavioral value by disclosing the out-of-band approval link sent to the owner and a 'Free' cost note, but it omits reversal, auth requirements, and what happens on failure.

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?

Very short and front-loaded, which is good, but the clipped fragments 'Never: Activate production. Free.' are cryptic rather than economical — they consume space without conveying actionable meaning to an agent.

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 mutation tool with nested objects, an enum-constrained scopes list, and no output schema, the description is far too thin. It never explains the mandate lifecycle, required identifiers, or what the returned approval link implies, leaving major gaps an agent must guess at.

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 only 17% across 6 parameters, so the description carries the burden — and it describes none of them. Required nested objects (delegate, scopes), the whatsapp channel constraint, expires_in_days limits, and the paid_by default are left entirely to the schema, with paid_by being the only field with any schema prose.

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?

States a specific verb+resource ('Creates a mandate') and adds a distinguishing side effect ('the out-of-band approval link for the owner'). It does not, however, distinguish itself from siblings like assign or job_create, and the trailing 'Never: Activate production. Free.' fragments muddy rather than sharpen the purpose.

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?

No when-to-use, prerequisites, or alternative-tool guidance is given. 'Never: Activate production' is an opaque boundary that an agent cannot map to a decision, and no sibling is named as the fallback for other cases.

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