list_coaching_styles

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful authorization context (`coaching:read`) and content coverage (built-in and team styles), but does not mention return shape, ordering, or pagination; with annotations carrying safety, a 3 is appropriate.

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?

Two short lines with no filler, and the resource category is front-loaded. The first line is a fragment and could be a complete sentence, but it is appropriately terse for a zero-parameter list tool.

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 zero-parameter list tool, it gives the key authorization scope and indicates the two style categories. It still does not explicitly say it returns a list or whether built-in and team styles are combined, leaving a small inference gap despite the low complexity.

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?

There are no parameters, so parameter semantics are minimal by definition. The empty schema is self-contained, and the description introduces no parameter-related confusion.

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 names the resource and its scope (built-in and team coaching styles), but omits an explicit verb; it reads as a title fragment rather than 'lists'. The plural name and create/update siblings imply a read operation, but the action is not stated in the description itself.

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?

It provides the required OAuth scope `coaching:read`, but gives no guidance on when to choose this tool over `create_coaching_style` or `update_coaching_style`, nor when not to use it. A prerequisite scope is useful but is not a when-to-use guideline.

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