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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the details are 'public' and that returned URLs should be preserved exactly, which is useful context beyond annotations, but it does not cover missing-slug behavior or other operational details.

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?

Two short sentences, with the core action front-loaded and no wasted wording. The second sentence is a compact instruction about preserving returned URLs.

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?

The tool is simple and has an output schema, full parameter description coverage, and clear read-only annotations. The description covers purpose and a notable output-handling constraint, so it is nearly complete; only minor edge-case behavior 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?

Schema description coverage is 100%, and the schema already explains that slug is the identifier returned by search_robots. The description only restates 'by slug' and adds no syntax, format, or validation detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 a specific verb (Get) and resource (robot details/specifications) with a clear lookup key (slug). It distinguishes a single-record fetch from list/search tools by saying 'one robot by slug', though it does not explicitly name search_robots as the sourcing alternative.

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?

Usage is implied: fetch one robot using a slug, and the schema notes the slug comes from search_robots. There is no explicit when/when-not guidance or alternative routing in the description itself. The 'Preserve returned URLs exactly' sentence gives downstream handling guidance but not selection guidance.

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