Api metrology metric instances object retrieve

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered without the description. However, the description adds no behavioral context at all — nothing about what object is returned, whether it 404s on unknown id, or what 'object' semantics mean here.

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 short, but brevity here is under-specification rather than conciseness: the single token conveys no information beyond the already-visible tool name, so no sentence 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 retrieve tool with an undocumented required id and no output schema, the description should at minimum describe the returned resource; it provides nothing, leaving the agent with only the annotations.

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?

There is one parameter (id) with 0% schema description coverage, and the description provides no clarification of what kind of identifier it expects or where it comes from. With zero coverage and no compensating text, the parameter is effectively undocumented.

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 a verbatim restatement of the tool name ('api_metrology_metric_instances_object_retrieve'), which is a tautology rather than an explanation. It does not distinguish this tool from close siblings such as metric_instances_retrieve, metric_instances_list, or metric_instances_object_retrieve, so an agent cannot tell which one fetches a single instance object.

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 tool versus the many sibling metrology tools (list, retrieve, cascade_info_retrieve, status_retrieve). No conditions, prerequisites, or alternatives are given.

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