get_all_coaches

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

No annotations are provided, so the description must carry the full burden. It mentions pagination, which is a key behavioral trait, but fails to disclose other important aspects such as authentication requirements, rate limits, data freshness, or what 'available within your subscription' entails. The minimal disclosure leaves significant gaps for an AI agent.

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 of 8 words, concise and front-loaded with the key verb and resource. Every word earns its place with no redundancy or 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 that the tool has 6 optional parameters, no output schema, and no annotations, the description provides the basic purpose and pagination but lacks completeness. It does not explain the scope of 'available within your subscription' or any constraints. For a simple listing tool, it is adequate but could be more informative.

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 has 100% coverage with descriptions for all 6 parameters. The tool description does not add any additional meaning beyond the schema. Baseline score of 3 is appropriate as the schema does the heavy lifting, and the description provides no extra parameter context.

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 'Get all coaches available within your subscription (paginated).' It specifies the verb, resource, and adds scoping (subscription-based) and pagination. This effectively distinguishes it from sibling tools like get_coach_by_id, get_coaches_by_country_id, and search_coaches_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 description implies usage when you need all coaches, but it does not provide explicit guidance on when to use this tool versus alternatives like get_coaches_by_country_id or search_coaches_by_name. Given the rich sibling context, more explicit differentiation would be helpful. Score reflects implied but not explicit guidance.

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