Api metrology metric instances list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The phrase about injecting "optimized data into the serializer context" weakly implies enriched/pre-joined results, but says nothing about pagination, filtering behaviour, or permissions.

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 short sentence, but brevity here is under-specification rather than concision. The one clause present conveys implementation detail instead of the resource, action, and filters an agent needs.

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 14-parameter list endpoint with no output schema and no parameter documentation, the description supplies none of the missing information. An agent could not infer what is returned, how filters combine, or how pagination via limit/offset/max_pages works.

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?

Fourteen parameters with 0% schema description coverage, and the description mentions none of them. Filters such as id, owner, folder, status, ordering, max_pages, filtering_labels, metric_definition, collection_frequency and organisation_objectives are left entirely unexplained in both places.

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 text "Override the list method to inject optimized data into the serializer context" is an internal implementation note. It never names the resource (metrology metric instances), so an agent cannot tell from it that this lists metric instances rather than any of the many sibling *_list tools.

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?

No statement of when to use this tool, when not to, or how it relates to siblings like metrology_metric_instances_retrieve or metric_instances_cascade_info_retrieve. The sentence reads as a code comment and actively misdirects rather than guiding selection.

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