cja_list_calculated_metrics

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

With no annotations, the description details filtering, pagination, and expansion options. It discloses read-only behavior and no destructive actions, though it omits rate limits or authentication requirements.

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 well-structured with a summary, parameter details, return info, and examples. It is slightly lengthy but each sentence is meaningful and earns its place.

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 list tool with 7 parameters and no output schema, the description covers arguments comprehensively and provides usage examples. It lacks detail on the return structure beyond a dictionary with list and count, which is adequate.

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 descriptions are absent (0% coverage), but the description explains each parameter's purpose, options, and defaults clearly, adding significant value beyond the schema itself.

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 tool lists calculated metrics in CJA, explaining they are custom formulas for reports. This distinguishes it from siblings like cja_get_calculated_metric_details (single metric) and cja_create_calculated_metric (creation).

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 filter parameters and example queries guiding usage. It does not explicitly exclude when to use alternatives, but the context and examples imply proper use, e.g., listing vs. getting details.

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