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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds no further behavioral detail such as response format, error handling, or authorization requirements, merely restating that it retrieves attribute values.

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 description is brief but redundant, repeating 'specific instance' and using awkward phrasing like 'attributes values to a specific instance.' It could be tightened to one clear sentence.

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 simple get-by-id tool, the description is minimally adequate for selection but lacks output format details and parameter explanations. The absence of an output schema and the low parameter coverage make invocation less safe, especially with no guidance on the required x-request-id.

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?

The schema provides no descriptions for any of the three parameters (0% coverage). The description only hints at instanceId via 'by id' but does not explain the required x-request-id header or the optional x-trace-id, leaving the agent to infer their purpose from names alone.

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 clearly identifies the action as retrieving a single instance by id, using 'Get specific instance by id' which differentiates from siblings like retrieveInstancesList. The phrase 'attributes values' adds a bit of detail about what is returned, making the purpose clear.

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 on when to use this tool versus alternatives such as retrieveInstancesList or retrieveImage. The only contextual hint is 'on your account,' which doesn't clarify prerequisite conditions or alternative selection.

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