get_activity_gear

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description's only additional claim is that it returns an array, which is mildly useful given there is no output schema, but "verified live" is opaque jargon that conveys no actionable behavior.

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?

It is short, but that brevity comes from under-specification rather than efficiency — the one sentence is filler with no informative content, and "verified live" is unearned.

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 carries the burden of explaining what is returned, and it provides only "an ARRAY" with no indication of element shape, gear fields, or the relationship between the activity and its gear. For a retrieval tool with many gear-related siblings, this is far from 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?

Schema description coverage is 100% for the single activityId parameter, so the schema already documents the input fully. The description adds no semantics beyond that, which is the baseline case when the schema does the heavy lifting.

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 never states what the tool does. "returns an ARRAY, verified live" describes an output shape and an unexplained quality claim, not a verb+resource; an agent only learns the purpose from the tool name itself. It is neither a specific purpose statement nor even a restatement of the title.

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?

There is no when-to-use, when-not-to-use, or alternative guidance at all, despite many siblings (get_gear, get_gear_activities, get_gear_stats, get_gear_defaults, add_gear_to_activity, remove_gear_from_activity) that an agent could easily confuse with this one.

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