analyze_aerobic_decoupling

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

The description discloses trimming of warm-up/cool-down by default and reporting insufficient data, which adds behavioral context beyond the readOnlyHint and destructiveHint annotations. It does not contradict annotations and provides useful operational detail.

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 concise, front-loaded sentences express purpose and a key behavioral default without any filler. Every phrase 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?

The description lacks essential details for an analysis tool: no output format, no units for decoupling, and no specification of sportType values. It mentions insufficient data but not what a successful result looks like. Given the lack of an output schema and low parameter coverage, the description is incomplete for correct invocation.

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 only 33% (trimPercent has a description, activityId and sportType do not). The description mentions trimming indirectly but does not clarify activityId purpose or sportType allowed values. It fails to compensate for the low coverage, leaving two required parameters ambiguous.

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 clearly states a specific calculation (aerobic decoupling) for a defined resource (completed running/cycling activity) with a method (comparing halves). It distinguishes from generic analysis siblings like analyze_completed_activity by naming the exact metric and scope.

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?

Provides strong context for when to use (completed running/cycling activity) but does not explicitly mention alternatives or when not to use. The agent can infer applicability from the description, but explicit routing to alternative tools would improve it.

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