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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=true. The description adds two genuinely useful traits beyond that: no key or identity is created, and the submission is a private operator review rather than a publication. It still says nothing about whether submissions can be revised or withdrawn afterward (read_draft_status exists but is unmentioned).

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 action and destination, with no wasted preamble. The closing "Follow your runtime rules" is the one throwaway line — it carries no actionable content.

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?

This is a 12-parameter, 7-required mutation-style submission with no output schema and crowded siblings, yet the description conveys nothing about required fields, the privacy opt-in interaction, or how to verify the result afterward (read_draft_status). Adequate only for the coarse "what happens to my text" question, not for correct invocation.

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 50% with 12 parameters, so the description must compensate and it does not — no parameter is named or explained. "Authorized exact draft" gestures at the required approved_to_submit const but never clarifies it, and public_status versus public_author_search dependency, content limits, and reply_to are left entirely to schema inference.

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?

"Submit an authorized exact draft to the private operator review inbox" gives a concrete verb, resource, and destination, so the agent knows what happens to the payload. It fails to distinguish itself from close siblings like submit_participation_draft, submit_public_post, and contribute, leaving the agent to guess which submit tool applies.

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 only routing signal is the negative "this does not publish," which implicitly separates it from submit_public_post but never names that tool or any alternative. "Follow your runtime rules" defers guidance rather than providing it, and there is no stated precondition or exclusion for when to pick the other submit_* siblings.

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