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

Annotations already declare this a safe, idempotent, closed-world read, so the safety profile is covered. The description adds real behavioral value beyond that: what comes back ('exact model IDs and printerBuildVolume objects') and the disambiguation rule for ambiguous matches. It says nothing about the limit/pagination behavior of a capped lookup.

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?

Three short sentences with zero filler, front-loaded with the lookup action before the return payload and the ambiguity rule. Every sentence earns its place.

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 usefully names the returned artifacts (model IDs, printerBuildVolume objects) and covers the multi-match case. Minor gaps remain: the search granularity implied by 'limit' and the no-match behavior are unaddressed.

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 coverage is 50%: 'query' is well documented with examples in the schema itself, while 'limit' is undocumented in both schema and description. The description implies name-based lookup but adds no syntax or interpretation guidance beyond the schema's own example.

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?

States a specific verb and resource ('Look up a named 3D printer in the Extrabold Tools catalog') and distinguishes itself implicitly from the generate_* siblings by framing its output as input for generation tools. It never names a specific sibling to route away from, so it stops short of full differentiation.

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?

Gives clear context for use: this resolves model IDs and build-volume objects 'ready for generation tools,' and it instructs the agent to ask the user to choose when multiple models match. It offers no explicit when-not or named alternative, so it is context without exclusions rather than a routing rule.

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