ddb_get_character

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is already known. The description adds valuable behavioral context by disclosing the login requirement and the default behavior of returning all sections ('full (default)'). No contradiction with annotations.

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 two sentences, front-loaded with the primary purpose, and immediately provides actionable usage details. Every sentence earns its place with no redundancy.

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 display tool with no output schema, the description is sufficient: it covers login prerequisite, section selection, and default behavior. It could be more explicit about the output format (e.g., text/markdown), but 'display' adequately implies a human-readable representation.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by expanding the sections enum into meaningful groupings (e.g., 'summary (vitals+stats)', 'combat (adds actions/weapons)', 'notes (backstory, traits, bonds)'), which helps the agent select the right section value.

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 a specific verb and resource: 'Parse and display a character sheet.' While it doesn't explicitly name sibling alternatives like ddb_get_character_raw, the phrase 'parse and display' implies a processed output that contrasts with raw retrieval, providing implicit differentiation.

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 gives clear usage guidance: 'Use sections to reduce output' and lists all section options with examples. It also provides a prerequisite: 'Requires login — run ddb_login first if you haven't already.' It doesn't state exclusions or when not to use, but the context is clear.

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