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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description usefully adds limits (65536 request bytes, 5 s execution), the 'software/model evidence only' scope, and 'candidate only when verified' outcome semantics. However, it never explains why a 'compare' operation is non-read-only (the paid-job/max_total_price nature implied by the schema), which is the most important behavioral fact an agent needs.

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 Problem/Input/Result/Limits structure is front-loaded and dense with no filler. Every clause carries information, though the telegraphic style sacrifices some readability.

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?

An output schema exists, so return values needn't be described. The description covers purpose, limits, and result shape, but given a deeply nested schema with 4 required envelope parameters at 0% coverage, the omission of parameter semantics and the paid-job/submission mechanics leaves meaningful gaps.

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% and there are 4 required parameters, so the description must carry the load. It only loosely names request-object contents ('predicted, observed, declared mapping, rules') and never explains the required envelope fields schema_version, idempotency_key, or particularly max_total_price, whose const value and role are opaque.

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?

States a specific verb (compare) and resource scope (digital-twin output vs. mapped observations against caller tolerances), which is more concrete than a generic 'compare' tool. It does not, however, differentiate itself from near-siblings like robotics_compare_planned_observed_trajectories_v1 or robotics_compare_state_estimators_v1, so an agent must still guess which compare tool applies.

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 'Problem:' framing gives context on what the tool is for, but there is no explicit when-to-use, when-not-to-use, or alternative routing among the many robotics_compare_* siblings. Nothing tells the agent when this is preferable to the trajectory or estimator comparison tools.

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