get_power_curves

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

No annotations are provided, so the description carries the full burden. It clearly states that the tool retrieves and analyzes power data, and returns a JSON string, implying a read-only operation. It adds value by describing the analysis behavior and return format, though it lacks explicit mention of edge cases or authentication requirements.

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 well-organized with a concise opener, a short analysis explanation, and structured Args/Returns sections. There is slight redundancy between the first two sentences ('best efforts' and 'peak power outputs'), but overall it is appropriately sized and easy to scan.

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 the simple read-only nature, the presence of an output schema, and full schema coverage for parameters, the description covers essential context. It also explains the parameter override and default, making it sufficient for an agent to correctly invoke the tool without ambiguity.

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 coverage is 100%, giving a baseline of 3. The description enriches parameter understanding by explaining that days_back overrides time_period and that time_period defaults to 90 days, which is not evident from the schema alone. This goes beyond the schema's basic descriptions.

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 uses a specific verb ('Get') and resource ('power curve data') with a clear scope ('best efforts for various durations'). It distinctly differentiates from sibling tools like get_hr_curves and get_pace_curves by focusing on power-specific analysis.

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 usage context: 'tracking performance improvements and identifying strengths/weaknesses across different power duration profiles.' It does not explicitly name alternatives or exclusions, but the context is sufficient for a user to understand when to use this tool.

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