tp_get_workout_note

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

Without annotations, the description only implies a read operation but does not disclose behavior like what happens if no note exists, authorization requirements, or response format.

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 a single sentence with no wasted words, making it concise and easy to parse. However, it could benefit from slightly more structure to include key behavior.

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 lack of output schema and only 50% parameter coverage in the schema, the description does not provide enough context on what the return value looks like or how it differs from similar 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 description adds no parameter-level details beyond the schema; the schema has 50% coverage (athlete described, workout_id not), and the description does not clarify the missing parameter's purpose.

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 'Get the private workout note for a workout' clearly states the verb ('Get') and the specific resource ('private workout note'), distinguishing it from sibling tools like tp_get_workout_comments (comments) and tp_get_note (general note).

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?

No guidance on when to use this tool versus alternatives, no context for prerequisites or when not to use it.

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