Discover workout and routine API

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

No annotations provided, so description carries full burden. It says 'find', which suggests a read operation, but doesn't explicitly state it's non-destructive or that it doesn't modify data. No mention of permissions or side effects.

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?

Single sentence, but overly generic and missing crucial details. It could be more concise by adding a brief explanation of output, but instead it wastes space on vague terms like 'fitness progress' without structural benefit.

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 complexity of the domain (multiple sibling tools for workouts) and lack of output schema, the description fails to provide enough context for correct tool selection. It doesn't explain what 'find' means or what kind of results to expect.

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 only parameter 'limit' is not explained in the description. With 0% schema description coverage, the description should clarify its purpose (e.g., how many results to return), but it omits this entirely.

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 it 'finds' schema operations and fields related to workouts, which is a specific verb and resource, but it's vague about what exactly is returned. It distinguishes from siblings by focusing on workout-related schema, but the lack of detail on output reduces clarity.

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 like ryot_schema_search or ryot_find_candidate_operations. The description implies it's for discovering workout schema, but doesn't state exclusions 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.