save_player_notes

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description still adds non-redundant behavior: the write is a full replacement of prior content, so read_coach_notes must be called first, and the payload must be Markdown under 100 KB. These constraints are not derivable from the structured fields.

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?

Effectively front-loaded: purpose, then when-to-use, then alternative, then the argument. The trailing "Args:" block partially restates "send the full updated text" from the body, a small redundancy, but no sentence is otherwise wasted.

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 one-parameter write tool with an output schema already documenting returns, the description supplies everything an agent needs: the destructive replace model, the read-before-write workflow, format, size limit, and sibling routing.

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 0% and the schema only types the parameter as a bare string, so the description carries the load: it specifies that text is the complete new content (not a delta), the Markdown format, and the 100 KB ceiling. Only a minor gap remains, such as behavior on invalid or oversized input.

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 ("Save the player notes") plus scope ("shared by all characters") and the replace semantics in the first sentence. An agent can distinguish it from the sibling save_coach_notes without opening either schema.

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?

Gives an explicit trigger ("when you learn how the player likes to be coached"), enumerates the kinds of content that qualify, and routes the one-character case to save_coach_notes by name. The read_coach_notes prerequisite is spelled out as part of the workflow.

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