origin_plot_matrix_id

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Create a graph', failing to mention side effects (e.g., overwriting existing graphs), error conditions, or required permissions. This is insufficient.

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 description is a single sentence of 15 words, which is concise. However, conciseness is not helpful when it sacrifices necessary content. The structure is adequate but the description is under-specified.

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?

Given 6 parameters (3 required) and no annotations, the description is highly incomplete. It doesn't explain the return value (output schema exists but not described), valid Plot Type IDs, template usage, or error handling. The complexity demands more detail.

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%. The description only repeats parameter names ('data_range', 'plot_type_id', 'template') without adding meaning. It does not explain what valid values are, how they interact, or any constraints.

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 'Create', the resource 'graph', and the source 'existing matrix/XYZ Origin range' using a Plot Type ID. It distinguishes from sibling tools like origin_plot_from_range by specifying the matrix/XYZ range input. However, it could be more explicit about when to prefer this tool over others.

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 provides no guidance on when to use this tool, what prerequisites are needed, or how it differs from alternatives. There are no explicit when-to-use or when-not-to-use statements.

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