origin_plot_style_capabilities

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

No annotations provided, so the description must fully disclose behavior. It only states the tool lists controls, omitting details like pagination, performance, or side effects. The minimal description leaves important behavioral aspects unknown.

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?

A single, concise sentence that front-loads the action and resource. No unnecessary words, and the structure efficiently communicates the core function.

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?

The tool has an output schema, so return values are documented elsewhere. However, the description does not explain the output's structure or provide enough context for an agent to decide when to use this tool among many similar siblings. It is minimally complete given the output schema.

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?

With 0% schema description coverage, the description adds conceptual meaning by mapping the three parameters to filtering criteria. However, it lacks details on valid values (e.g., what chart types or term formats are acceptable). Baseline reduced due to low coverage but description provides some semantic mapping.

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?

Description specifies verb 'List' and resource 'semantic plot style controls', with three filtering criteria (chart type, Plot Type ID, term). This clearly identifies the tool's function and distinguishes it from sibling plotting tools that create or modify plots.

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 versus alternatives like 'origin_plot_style_setter_coverage' or 'origin_set_plot_style'. The description does not specify prerequisites or contexts where this tool is preferred.

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