Api metrology dashboards update

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that — no indication of what fields are replaced, whether unspecified fields are preserved (full update vs partial), or what permissions are needed.

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?

A single bare token is technically terse but is under-specification rather than conciseness. There is no front-loaded verb-plus-object sentence an agent could act on.

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?

This is a mutating endpoint with an untyped body parameter, no output schema and no description content whatsoever. For a write tool where the payload shape is undefined, the definition is completely inadequate.

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 description supplies no parameter meaning at all. The required 'id' and the untyped, free-form 'body' object are left entirely unexplained, so the agent cannot know what shape of payload this endpoint expects.

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 literally the tool identifier 'api_metrology_dashboards_update', which restates the name/title rather than describing the operation. An agent can infer 'update a metrology dashboard' only by parsing the identifier itself; nothing distinguishes it from siblings like metrology_dashboards_partial_update or dashboards_retrieve.

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 mention of the sibling partial_update / create / retrieve variants, and no stated prerequisites. With dozens of metrology_dashboards_* siblings, the absence of routing information is a real failure, not just an omission.

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