get-actor

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns minimal metadata without descriptions and is optimized for token usage. It also notes that identifier can accept a token ID for live state. However, it does not explicitly state that the operation is read-only or safe, which would improve transparency.

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 with four sentences and a clear structure: purpose, what is returned, when to use, and alternative. It front-loads the core purpose. While efficient, it could be slightly more compact by merging the last two 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?

Given no output schema, the description covers the return data comprehensively: stats, actions, effects, items with minimal metadata. It also addresses the token ID use case. The description is complete enough for an agent to understand what to expect.

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?

The input schema covers the identifier parameter with a brief description. The tool description adds significant value by explaining that the identifier can be a character name/ID or a token ID, and elaborates on how token IDs work (live state, unlinked NPC can differ), which is not present 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 clearly states the tool retrieves D&D 5e character info optimized for minimal token usage, listing specific returned data (full stats, action names, active effects/conditions, items with minimal metadata). It distinguishes itself from the sibling tool get-actor-entity by directing users to that tool for full details.

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 description explicitly states when to use this tool ('Perfect for checking equipment or identifying what to investigate further') and when not to use it ('Use get-actor-entity to fetch full details for specific items, spells, or effects'), providing clear guidance on alternatives.

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