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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive behavior. The description adds meaningful behavior beyond that: current versus sealed body handling, assignment overrides, errors for unnumbered entries and collisions, and no aggregation or truncation.

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?

The purpose is front-loaded and the details are dense but relevant. No sentence is obviously wasted, though the wording is packed enough that it takes careful reading.

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 five-parameter render tool with nested objects, enums, annotations, and an output schema, this is largely complete. The only notable omission is an explanation of the scheme choices.

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%, so the description must carry the burden, and it largely does. It explains body_version defaults and version meanings, item_ids defaults to posting accounts, and assignments are keyed by stable ID and restricted to the current body; only scheme's values are left unexplained.

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: renders a readable standard chart. The clause 'Does not alter, seal or install the chart' helps distinguish it from create/update-like siblings, though no sibling is named explicitly.

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 this is a rendering/preview operation rather than a mutation. It does not explicitly state when to use it instead of create_standard_chart, update_standard_chart, or list_chart_accounts.

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