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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully confirms there is no financial side effect despite the open-world contact, and adds the "one token and idempotency key per task, including across swarm retries" retry contract, but says nothing about what happens after submission (queued, reviewed, rejected) or any auth requirement.

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?

Three short sentences, front-loaded with the operation and the strongest disambiguator ("No charge or booking") before the retry mechanic. Nothing is padded, though the final sentence mixes two separate concerns (token and idempotency key) into one clause.

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 write tool with a nested object requiring nine fields, no output schema, and a review-based workflow, the description is thin: it never explains what the brief must contain, what review means for the caller, or what the invocation returns. The retry guidance is the right instinct but does not fill the structural 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 67% and the two token-related parameters already carry their own descriptions, so the schema does most of the work. The description adds genuinely new meaning for requestToken and idempotencyKey (hold one per task across swarm retries), but contributes nothing about the nine required fields inside the nested brief object, which is where an agent is most likely to err.

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 and resource ("Submit an authorized brief for human review") and immediately scopes it away from transactional siblings with "No charge or booking", which separates it from create_payment_checkout and accept_quote. It does not name those siblings explicitly, so differentiation is implied rather than stated.

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 charge or booking" gives a useful negative signal about when to prefer this over the payment tools, and "for human review" implies the workflow stage. However there is no explicit when-to-use clause, no statement of prerequisites beyond "authorized", and it never names an alternative to route to.

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