my_characters

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

The description discloses authentication needs ('requires their stored API key') and details output behaviors (aggregated inventory, name_filter support, upgrades/stats preserved, action field handling). It does not explicitly state read-only or destructive nature, but the content suggests read-only. Without annotations, this is strong 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 information-dense with clear bullet-style explanations. It front-loads the main purpose and each sentence adds value. However, it could be more structured (e.g., numbered sections) for easier parsing.

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 the tool has an output schema (context signal: has output schema: true), the description effectively covers parameter usage, section behaviors, and special handling of action field. It provides sufficient context for an agent to use the tool correctly without needing additional details.

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 has 0% coverage, but the description thoroughly explains each parameter: name is needed for detailed sections, section selects data type, name_filter works in inventory. This adds significant meaning beyond the bare schema, enabling correct invocation.

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 the user's characters with their API key, and distinguishes different sections (list, overview, inventory, equipment, crafting) with specific output characteristics, differentiating it from sibling tools like my_account or my_storage.

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 explains when to use each section (e.g., 'section="list" (no name needed): character names') and implies authentication requirements. It does not explicitly state when not to use it or provide alternative tools, but the context of sibling tools and clear section explanations gives good guidance.

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