compare_volumes

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

With no annotations and no output schema, the description carries the full behavioral burden, yet it discloses nothing about whether the call is read-only, what it returns, whether it cooks or evaluates the scene, or what permissions/costs are involved. The only hint is that the result is per-band, which is not enough for a 5-parameter analysis tool with zero annotation coverage.

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?

One short sentence with no padding and the key idea front-loaded, so it is concise. However, brevity here comes at the cost of specification rather than from efficient wording, leaving the agent with a riddle rather than a definition.

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?

Five parameters, three of them required, no annotations, no output schema, and no parameter documentation anywhere. The description supplies none of the information an agent needs to invoke this tool correctly, so it is inadequate for the tool's complexity.

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 compensate and does not. It loosely implies the roles of field, against, and bands, but says nothing about node_path, against_node, the default of 10 bands, or the accepted format of the bands array (integers vs. explicit edge lists).

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 sentence describes an operation in conceptual terms (one field's values distributed across bands of another field), but it uses no verb and no resource name, so the agent must guess that this is a binned-histogram comparison of volume data. Nothing in the text distinguishes it from the sibling compare_snapshots or clarifies what 'how much' measures (count, sum, percentage).

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The agent cannot tell from the description under what conditions this tool is the right choice versus compare_snapshots or the many node/network creation tools in the catalog.

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