get_activity

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

No annotations provided, so description carries full burden. It describes the return values extensively (power, cadence, zones, etc.) and notes it's a full detail retrieval inheriting from the 'get' operation. Does not explicitly state read-only or side effects, but the verb 'Get' and tool name imply safe read.

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 sentences, front-loaded with purpose, informative list of fields in second sentence. No extraneous words; every part adds 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?

Given no output schema, description fully explains return values with detailed examples. Simple parameter needs little explanation. Distinguishes from list_activities, making context complete for agent selection.

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 has 100% coverage for the single 'id' parameter with description 'The Activity ID.' Description adds only minor reinforcement ('by ID'). Does not provide additional semantics or constraints beyond 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?

Description clearly states 'Get FULL details of a specific activity by ID' with a specific verb and resource, and distinguishes from list_activities by noting it returns 100+ fields beyond what list_activities provides.

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?

Explicitly says 'Always use this when answering questions about a specific activity,' providing clear guidance for when to use. However, it lacks explicit when-not-to-use instructions or alternative tools beyond implicit contrast with list_activities.

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