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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description goes beyond them by disclosing the shape of the payload — canonical units, maker-published values, and provenance documents — which is genuinely useful behavioral context. It omits only edge cases such as unknown-robot handling.

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 front-loaded sentence with a tight three-item list ('each spec in its canonical unit, the value as the maker published it, the document it came from'), each element carrying distinct information. Nothing is padding and nothing is buried.

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?

With no output schema, the description carries the burden of describing returns, and it does so accurately by enumerating the three content categories. For a one-parameter read tool this is close to sufficient; only error behavior for an unrecognized robot is left unstated.

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?

With a single parameter at 100% schema description coverage, the schema already defines 'robot' fully, including the maxLength and the 'maker/model' example format. The description adds no further parameter meaning, so the minimum-viable baseline of 3 is appropriate.

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 states precisely what is returned for a single robot: every spec in canonical unit, the published value, and the source document. That is a concrete verb-by-implication plus resource, and 'on one robot' scopes it. It does not, however, contrast itself with the lookalike siblings find_robots or search_robots, so an agent must infer the distinction between detail-fetch and discovery.

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 statement that a known 'maker/model' identifier is required, and no routing to alternatives such as find_robots (resolve a name) or compare_robots (multi-robot). The singular 'one robot' hints at a detail lookup but the description never states the condition that selects this tool over its siblings.

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