get_activity_detail

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

Description discloses that segment_efforts contain only current activity segments, and mentions returns. No annotations provided, so description carries burden; it does well but could state read-only nature explicitly.

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?

Description is concise and front-loaded with purpose and return list. Every sentence adds value, though slightly more brevity could be achieved.

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 lists return fields, references sibling tools, and covers usage context fully. Provides enough information for an AI agent to understand and use the tool correctly.

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 covers activity_id fully, and description adds value by explaining where to find the ID and linking to list_activities. Schema coverage is 100%, so description adds useful extra context.

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?

Clearly states 'Get activity metadata by ID' and lists specific return fields, distinguishing from sibling tools like get_activity_streams and get_segment_effort_streams.

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 guides when to use this tool vs. alternatives: 'For segment analysis over time...use get_segment_effort_streams', 'For full activity time-series, use get_activity_streams'.

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