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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the shape of each returned row (provenance tier, how common, first symptom) and the fact that details live on a separate page. It stops short of stating ordering, volume or pagination behavior for the list.

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 clauses with the returned content front-loaded, followed by the deeper-lookup route and then the id source. Every clause earns its place; there is no restating of the title or filler.

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 one-parameter, read-only list tool with no output schema, the description covers what comes back, where to go for depth, and where to get inputs. Nothing an agent needs in order to call it correctly is missing.

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 100% and the single parameter is already documented with an example id in the schema, so the baseline of 3 applies. The description reinforces the single-platform scope and the list_platforms source, but adds no syntax or format meaning beyond what the schema states.

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 resource (documented failure modes) scoped to exactly one engine platform, and enumerates what the list contains: name, provenance tier, commonality, and first reported symptom. This is clearly separable from siblings like get_symptoms or get_recalls without opening any schema.

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?

Names two alternatives with the exact condition for each: get_page for root cause, diagnosis, fixes and parts, and list_platforms to obtain valid platform ids. The agent knows both the follow-up path and the prerequisite source, so no inference is needed.

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