origin_format_graph

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

No annotations provided, so description is the sole source. It does not disclose behavioral traits such as whether the tool modifies the active graph, whether rescale affects all axes, or potential side effects. The description is minimal and assumes domain knowledge.

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 of 13 words with no redundancy. Front-loads the verb and key objects, efficiently conveying the tool's purpose.

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?

Despite 6 optional parameters and an output schema, the description fails to explain context (e.g., tool modifies existing graph, prerequisites like active graph). Lacks information about default behavior and return values, which is critical given the low schema coverage.

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 add meaning. It maps to 5 of 6 parameters: 'graph long name' (graph_name), 'axis labels' (x_label, y_label), 'legend visibility' (show_legend), 'optional rescale' (rescale). However, it omits the 'title' parameter and does not clarify that all parameters are optional with null defaults. Partially compensates.

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 clearly states the verb 'Set' and the resource 'graph' with specific properties (long name, axis labels, legend visibility, rescale). It distinguishes from sibling tools like origin_plot (creates graphs) and origin_set_axis (sets axis properties).

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?

No guidance on when to use this tool vs alternatives. Does not specify prerequisites (e.g., graph must exist) or exclusions (e.g., use origin_set_axis for axis properties). The description implies use for formatting, but lacks context.

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