compare_models

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. Beyond naming the action, it does not state whether the tool is read-only, what output format is returned, whether any side effects occur, or any prerequisites. 'Compare' suggests a read operation, but this is inference, not disclosure.

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 front-loaded sentence with no wasted words. It packs the verb, the resource, the scope ('multiple'), and the specific comparison dimensions into a compact, scannable form.

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?

With one required parameter documented in the schema, no annotations, and no output schema, the description gives the core purpose but omits behavioral context such as read-only status and return format. It is adequate for a straightforward comparison tool but leaves the agent to infer important execution details.

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?

The tool description does not mention model_ids, and the schema coverage is reported as 0%, so a strict reading says the description fails to compensate. However, the input schema itself contains the description 'List of model IDs to compare' for the sole parameter, which fully explains its meaning. The description adds contextual value by stating what the comparison covers, but does not directly elaborate the parameter syntax.

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 uses the specific verb 'compare' with a clear resource: 'multiple fitted MMMs', and names the aspects compared: diagnostics, predictive metrics, and lineage. This clearly distinguishes it from siblings like diagnose_mmm (single-model diagnostics) and select_best_model (selecting one), so an agent can tell them apart.

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 implies the appropriate use case—when multiple fitted MMMs need to be compared—but provides no explicit guidance on when not to use it or which alternative to choose. It never mentions select_best_model or diagnose_mmm as alternatives, so usage context is implied rather than stated.

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