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

Annotations only say this is a non-read-only, non-destructive, non-open-world call. The description goes much further: entries remain drafts until a human confirms each one in the Drafts view, they read as low confidence because they were written after the fact, the caller should report how many drafts are waiting and where to review them, and the call 'may return needs_confirmation'.

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?

Front-loads what the tool produces before prescribing history conventions, and each sentence carries operational content. Some prescriptive prose ('say so plainly rather than overstating them') is stylistic guidance rather than tool semantics, but for a tool with 50 nested draft objects the length is defensible.

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 complex, nested, no-output-schema tool this covers the draft/confirmation model, the history workflow and the key field conventions well. The two auxiliary parameters (workspace, approvalId) and the shape of a normal success response beyond needs_confirmation remain unexplained.

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 50%, and the description compensates substantially: fromHistory's meaning, that landedAt should be the ship/launch date taken once from the source, that source URL should be attached, and that rollout stays 'full' unless the source says staged or held-out. workspace and approvalId are still unexplained in both places.

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?

Opens with a specific verb and resource: writes up to 50 ledger entries as DRAFTS that stay out of the record until confirmed. That draft semantics is exactly what separates it from the sibling ledger_entries_create, so an agent can discriminate without opening either schema.

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?

Gives a clear triggering condition — 'entries you found rather than were told', such as decisions in meeting notes or a team's past changes read from its tracker, PRs or launch posts — and ties it to the fromHistory flag. It never names ledger_entries_create as the alternative for direct writes, so the when-not is left implicit.

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