Open AI Coach dashboard

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

Annotations already declare readOnlyHint=true, and the description reinforces it with 'Read-only.' It adds useful behavioral context beyond the annotation by specifying that it opens an interactive dashboard showing current mascot state. No contradiction.

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 sentences, front-loaded with the primary action and resource. 'Read-only' is a single reinforcing word, and there is no 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?

For a simple zero-required-parameter tool with annotations and an output schema, the description is sufficient: it states what is shown, that the view is interactive, and that the operation is read-only. Remaining parameter details are covered by the schema.

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?

Schema coverage is 100%: the single optional locale parameter is fully described with BCP 47 guidance and the note that hostContext.locale is passed through. The tool description itself adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb and resource: 'Show the current state of the AI Coach desktop mascots' and 'open an interactive dashboard.' This clearly differentiates it from siblings like read_ai_coach_note, show_ai_coach_message, and refresh_ai_coach_status.

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 use case is implied: use when a current-state overview or dashboard view of mascots is needed. However, it does not explicitly say when to prefer this over refresh_ai_coach_status or the show_ai_coach_* tools, nor does it state exclusions.

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