TrainingPeaks-MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the tool is 'rarely needed' which is useful context, but doesn't describe what the tool actually returns, whether it requires authentication, any rate limits, or what happens when invoked. The description is insufficient for a tool with zero annotation coverage.

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 extremely concise - just two brief sentences that both add value. The first states the purpose, the second provides crucial usage guidance. There's zero wasted language and it's perfectly front-loaded with the core functionality.

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?

For a tool with no annotations and no output schema, the description is incomplete. It doesn't explain what an 'athlete profile' contains, what format it returns, or why it might be needed despite being 'rarely needed.' Given the lack of structured data elsewhere, the description should provide more complete context about the tool's behavior and outputs.

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?

The tool has zero parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to compensate for any parameter documentation gaps. A baseline of 4 is appropriate for a zero-parameter tool.

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 states the tool 'Get athlete profile' which is a clear verb+resource combination, but it doesn't specify what information the profile contains or how it differs from other athlete-related tools. It's not tautological but remains somewhat vague about the specific nature of the profile data.

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 explicit guidance about when NOT to use this tool ('Rarely needed - other tools work without it'), which helps the agent understand this is a specialized tool. However, it doesn't specify exactly when it IS needed or which specific alternatives to use in different scenarios.

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