Api metrology metric instances partial update

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile exists in structured data. The description adds nothing on top: it doesn't mention that 'partial' means PATCH-merge semantics, whether unlisted fields are preserved, or what happens on re-application given non-idempotency. It does not contradict the annotations, but it contributes zero additional behavioral context.

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?

It is a single token, so nothing is wasted, but that brevity comes from under-specification rather than efficiency. There is no front-loaded explanation of purpose, scope, or payload shape.

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 write operation whose entire payload is an opaque object, with no output schema and no parameter descriptions, the definition leaves an agent unable to construct a valid call. It is nowhere near complete enough 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% and the only non-id parameter, body, is an untyped anyOf object with no field documentation. The description does nothing to compensate, so an agent has no idea what payload keys are accepted or valid.

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 is just the operation identifier restated verbatim, offering no verb+resource explanation beyond what the name already encodes. An agent can infer only that it's a partial update of 'metric instances' from the token string itself, with no clarification of what a metric instance is or what the update affects.

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 guidance whatsoever on when to use this instead of metric_instances_update (full replace) or metric_instances_create/destroy. With dozens of near-identical siblings in the metrology family, the absence of routing guidance is a real cost.

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