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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the agent knows this is a non-destructive write to a closed system. The description adds useful state context that saved drafts become pending posts awaiting review/queueing, but it omits validation behavior, limits (e.g. 20 drafts), and what happens on partial 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?

A single efficient sentence that front-loads the action and outcome with no filler. It could have used its brevity budget for one clause on required inputs, but nothing present is wasteful.

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 5-parameter nested write tool with 0% schema coverage and no output schema, the description leaves too much unexplained: platform values, project targeting, voiceGuide purpose, and confirmation of what is returned. The annotations carry the safety profile, but parameter and behavioral gaps remain significant.

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% across 5 parameters, including nested draft segments, pillar, platform enum, projectId, projectName, and voiceGuide. The description only mentions 'drafts you wrote' and adds no meaning for the platform enum, project scoping fields, or the voiceGuide object, so it fails to compensate for the undocumented schema.

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?

The description gives a specific verb ('Save') and resource ('drafts you wrote'), plus the resulting state ('as pending posts'), so the agent can tell this writes drafts rather than approving or rejecting them. It does not explicitly contrast with siblings like approve_drafts or edit_draft, which keeps it from 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 'so they can be reviewed and queued' implies when this fits in the workflow: draft creation before review/queueing. There is no explicit when-not guidance, no mention of approve_drafts/reject_drafts as alternatives, and no prerequisites such as a linked account requirement.

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