Get All Gear

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

The annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe, unrestricted read operation. The description adds that it returns UUIDs and covers all gear, which is useful context, but it doesn't mention potential large response size or any data organization beyond the fact that it's a 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?

The description is two concise sentences, front-loaded with the core purpose and followed by a meaningful rationale. Every sentence earns its place with no redundancy 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 zero-parameter, read-only tool with no output schema, the description adequately explains what the tool returns (full list with UUIDs) and why it's valuable. It could theorize about pagination or response size, but the simple scope and annotations make this relatively complete.

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?

The input schema has zero parameters, so the baseline is 4. The description actually adds meaning by clarifying that the output includes UUIDs, which addresses the schema's lack of parameters. No parameter-level guidance is needed since there are none.

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 states 'Get complete list of all gear/equipment with their UUIDs', which is a specific verb+resource combo. It clearly establishes the full scope ('all gear') and differentiates itself from sibling tools like get_gear_stats or get_gear_collection by focusing on the complete list with UUIDs.

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?

The description provides clear context by explaining 'This solves the UUID problem - you can now discover all gear without needing to manually find UUIDs in the web interface'. It implies when to use it (UUID discovery), but does not explicitly name alternatives or exclusions, like when to use get_gear_stats or get_gear_activities instead.

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