Name Character

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

Discloses non-idempotency, overwriting behavior, lack of confirmation/uniqueness check, and the exact return format. Annotations indicate readOnlyHint=false and destructiveHint=false, and the description adds specifics beyond these (overwrite semantics, no uniqueness check) without 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?

The description is concise yet complete: front-loaded purpose, automatic-call note, usage guidance, idempotency warning, and return format—all in a few well-structured sentences.

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 1-parameter tool, it covers purpose, automatic invocation, when to call directly, behavior (overwrite, no checks), and return schema, leaving no ambiguity for the agent.

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?

Despite zero schema description coverage, the description explains player_name is the player-chosen name with no format constraints, adding meaning not in the schema. It also clarifies the return value with that parameter.

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 'Set the name of the character being created for a new Sitting' with a specific verb and resource. It also distinguishes itself from siblings by noting it's automatically called and exists for other tools to validate against.

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?

Explicitly explains when it's called automatically, that users typically don't need to call it, and provides clear guidance for when to invoke it directly (renaming outside the normal flow). This distinguishes it from alternatives.

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