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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds nothing beyond what the endpoint string implies — no mention of 404/not-found behavior, whether fields/expand affect the shape, or rate limits.

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 nothing extraneous, but the second sentence merely restates the two already-required path parameters and carries no added meaning. Efficient in length, thin in value.

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 simple single-record read with full schema coverage and read-only annotations, this is minimally adequate. It omits what the response looks like and whether a missing equipment_id returns an error, which the lack of an output schema would otherwise require.

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%, so all four parameters (customer_id, equipment_id, expand, fields) are already documented in the schema. The description adds no interpretation beyond the path parameters, so baseline 3 applies.

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 says it returns 'one piece of equipment of a customer' and gives the GET path, which implies a single-record retrieval. But it is a noun phrase with no verb, and the singular-vs-list distinction against servicefusion_list_customer_equipment is only implied by 'one', not stated.

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?

No guidance on when to use this versus listing equipment first, or versus the parent customer lookup. The only hint is the schema note on equipment_id ('from servicefusion_list_customer_equipment'), which is in the schema, not the description.

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