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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds real context beyond that: only 'active' models are eligible, UUIDs are never returned, and the payload includes canonical URL, specifications, description, and live-stock count.

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 dense sentences ordered purpose → usage → return contents, with no filler. Slightly information-packed but every clause 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 correctly enumerates what is returned (canonical URL, specs, description, live-stock count), and annotations cover the safety profile. The remaining gap is the requiredness/relationship among the three lookup parameters.

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%, so the description must carry parameter meaning; it does explain the role of each identifier (slug preferred, UUID legacy-only) and ties vehicleType to the slug path. However, it never states that at least one of id/slug is effectively required nor describes the allowed vehicleType values, so the gap is only partly closed.

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 ('Fetch ... research details for one active RoamWorthy model') with scope ('one active'). It also implicitly separates itself from the list-oriented sibling search_models by pointing there as the source of identifiers.

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?

Explicitly names the alternative (search_models) and states the preferred input path ('Prefer model slug plus vehicle type'), while documenting the fallback ('legacy UUID lookup remains accepted for compatibility'). An agent knows exactly which parameter combination to send and where to get it.

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