get_chart

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

Describes returned properties (position, size, etc.) and states 'return effective state', implying a read operation. No annotations exist, so description carries full burden. Missing details on side effects, auth, or rate limits, making it moderately transparent.

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?

Single sentence listing many output fields; no wasted words. Efficient but slightly dense. Could benefit from minimal structuring (e.g., bullet points), but overall concise.

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?

Lists output fields in detail, partially compensating for lack of output schema. However, it ignores parameter documentation entirely. Given two required parameters and no schema descriptions, more completeness is needed.

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 0% and description does not explain the two required parameters ('name' and 'path'). Only mentions 'named Chart' which hints at 'name', but no elaboration on 'path' or parameter semantics. Fails to compensate for missing schema descriptions.

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?

Clearly states it returns the effective state of a named Chart with a detailed list of components. The reference to symmetry with get_textbox/get_image/get_rectangle distinguishes it from sibling tools for other item types.

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?

Implied usage for obtaining chart state, but no explicit when-to-use or alternatives. The symmetry note provides some context but lacks guidance on when not to use it or prerequisites.

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