get_workout_surveys

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal that the return is a map of ID to survey data containing specific question types, which is useful. However, it does not mention any side effects, permissions, error behavior, or whether it is read-only, leaving some uncertainty.

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 two compact sentences, front-loaded with the main action and return structure. Every word adds value, no redundancy or irrelevant details.

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 simple retrieval tool with one parameter and no output schema, the description covers the input, the output structure, and the data fields. It doesn't specify behavior for invalid IDs or limits, but this is a minor gap given the simplicity.

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 input schema only defines a field name and type with no description, giving 0% schema coverage. The description compensates by explaining the parameter is for saved workout IDs and how they map to the returned survey data. It adds clear semantic meaning beyond the raw schema.

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 the tool retrieves pre/post workout surveys for specific saved workout IDs. It uses a specific verb 'Get' and a specific resource 'workout surveys', distinguishing it from sibling tools that handle messages, leaderboards, or history.

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 implies usage when survey data is needed for known workout IDs, but does not explicitly mention alternatives or exclusion criteria. For example, it doesn't distinguish itself from get_workout_details or get_workout_messages, though the resource is different. This is implied usage rather than explicit guidance.

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