recent_history

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: results are newest-first and the character argument falls back to the most recently saved character, which materially affects behavior. Return shape is covered by the output schema, so nothing critical is missing.

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?

Front-loaded purpose sentence, then a single usage sentence with two concrete examples, then a compact Args block. No filler, and the ordering guarantee is stated in the first line where an agent will see it.

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?

All optional parameters are explained, annotations cover the safety profile, and the output schema handles return values. For a two-optional-parameter read tool, an agent has everything needed to call it correctly.

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%, so the description must carry the full burden, and it does: character accepts a name or "Name-Realm" form, is case-insensitive, and may be omitted to target the last saved character; limit is capped-count with a stated default of 20. Remaining gaps are minor, such as what happens on an unrecognized character name.

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?

Specific verb and resource: "Get a character's recent events" with concrete event categories (level-ups, deaths, quests) and an ordering guarantee (newest first). It does not explicitly distinguish itself from close siblings like character_status or progress_summary, which also report on player state, so an agent must infer the boundary.

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 concrete when-to-use triggers: "to explain a death" and "to track progress between coaching sessions." No when-not guidance and no explicit pointer to an alternative tool, leaving overlap with progress_summary unresolved.

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