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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds useful context the annotations lack: the created record starts in DRAFT and is intended to flow through an approval pipeline, plus an enterprise feature gate. It omits behavioral details such as permission requirements or side effects like notifications/reviews triggered.

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, front-loaded with the core action and no filler. The parenthetical '(DRAFT to APPROVED/REJECTED)' is compact but slightly ambiguous about whether this tool performs the transition or merely feeds it, which is the only structural blemish.

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 13-param creation tool with no output schema, the description covers purpose, initial state, and feature gating but omits what the call returns, required permissions beyond the feature tier, and how it relates to advance_proposal_stage/submit_proposal_review. Adequate but with clear gaps given the tool's complexity.

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?

With 13 parameters and only 46% schema description coverage, the description carries a larger burden but contributes nothing about parameters — no mention of title, priority, riskLevel, sponsorId, or the idempotencyKey retry behavior documented in the schema. Several params are self-descriptive by name, which keeps this above 1, but the low coverage is not compensated.

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 ('Create a DRAFT governance proposal') and pins the created object's initial lifecycle state, which distinguishes it from update_proposal and advance_proposal_stage. It does not name a sibling tool explicitly, so an agent must infer the boundary from the DRAFT-to-APPROVED lifecycle phrase.

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 description implies when to use it (creating a new proposal for review) and adds a real prerequisite via the 'governance (ENTERPRISE+)' gate. It offers no explicit when-not or alternative routing (e.g., 'to modify an existing proposal use update_proposal', 'to move stages use advance_proposal_stage'), leaving usage context implied rather than stated.

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