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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds useful behavioral context by stating the response includes the owning customer and site, plus the underlying endpoint (GET /equipment/details), but says nothing about errors when the exact name matches nothing or misses.

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 zero filler; the lookup keys and the returned context are front-loaded and the endpoint reference trails. 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?

No output schema exists, so the description's note that the result carries the customer and site is the only return-value signal and it is adequate. Combined with annotations covering the read-only profile and a fully documented schema, the definition is nearly complete, lacking only fallback behavior for a name that doesn't match exactly.

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 enum documents id/myId/name, so the baseline is 3. The description mirrors those three keys and adds the qualifier 'exact' for name matching, which is a small but genuine clarification beyond the schema.

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 ('Get') and singular resource ('One piece of equipment') and enumerates the three lookup keys. The singular framing implicitly distinguishes it from the sibling synchroteam_list_equipment, though it never names that sibling for explicit 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?

Usage is only implied by the phrase 'One piece... by id, myId or exact name', which signals a single-record lookup rather than a list. There is no explicit when-to-use statement, no exclusions, and no named alternative such as list_equipment for browsing.

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