Prepare AI Coach care

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

The readOnlyHint annotation already signals safety, and the description reinforces it with 'Does not change anything' and adds a workflow detail—user confirmation in the dashboard—that annotations do not convey. It also discloses the pre-change state in the output.

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 sentences, front-loaded with the tool's purpose and followed by the critical non-mutation note. No filler or redundant restatement of schema content.

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 read-only preview tool with an output schema, full parameter descriptions, and annotations, the description covers what the tool does, what it does not do, and the workflow context. Nothing needed to select and invoke it correctly is missing.

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 description coverage is 100%, so the schema carries the parameter semantics and the description need not repeat them. The description's action list is a useful gloss, though it uses 'walk' where the schema enum says 'toggle_walk'; the exact enum remains visible in the 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 states a specific verb ('Show'), a concrete resource (care actions for a mascot), and the key output (state before the change). It also clearly distinguishes itself from mutation tools by declaring it non-mutating.

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 establishes when to use the tool: to preview currently possible care actions before the user confirms in the dashboard. It does not explicitly name an alternative such as commit_ai_coach_care, but the non-mutating and confirmation-flow language makes the intended context clear.

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