get_enduraw_matrix

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

No annotations are supplied, so the description carries the whole burden; it does disclose the shape of the returned profile, which is real added value since there is no output schema. It omits whether the tool is read-only in effect, whether an athlete must be pre-selected in session/auth, and whether the result is cached or rate-limited — all material for a no-parameter fetch.

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?

A single sentence that front-loads the verb and resource, then parenthetically enumerates the payload. Every clause earns its place and there is no filler.

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, the field enumeration is the primary source of return-value knowledge and is helpful. However, for a no-parameter tool the critical unknown is what implicit subject (the authenticated athlete) the matrix is computed for, and that is never stated, leaving a real gap against a crowded family of sibling matrix tools.

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 accepts zero parameters, so per the baseline the schema requires no explanation and the description cannot add parameter meaning. The enumeration of returned fields partially compensates by telling the agent what the implicit context selects.

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?

States a specific verb ("Fetches") and a specific resource ("complete Enduraw Runner Matrix"), then enumerates the payload contents (aerobic endurance, climbing, downhill, speed, resilience, cohort percentiles). An agent can tell what comes back, but nothing distinguishes this from sibling get_enduraw_matrix_summary or get_enduraw_matrix_history by name.

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 word "complete" weakly implies this is the full-detail variant to use when a summary will not do, but the description never names matrix_summary or matrix_history as alternatives or states a selection condition. Usage is inferable rather than stated.

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