get-rolltable

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

No annotations provided, so description carries full burden. It details return content (every entry, roll range, weight, drawn flag, result text with enrichers, linked items) and sorting order (low-to-high). It implies read-only behavior ('Read', 'inspect or audit') without side effects. Sufficient for 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?

Two sentences front-loaded with the primary action and data details. Every clause serves a purpose: describes content, sorting, determinism, sibling contrast, and resolution method. No wasted words.

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 a single parameter, no output schema, and no annotations, the description thoroughly covers what the tool returns, its sorting, and its deterministic nature. An agent can fully understand the tool's behavior and output without additional information.

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 100% for the single parameter 'identifier', which already states 'Table id or exact name.' The description adds the phrase 'Resolves by id or exact name', slightly reinforcing but not adding substantial new meaning. Baseline 3 is appropriate.

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 uses a specific verb ('Read') and resource ('RollTable's FULL contents'), lists the exact data returned, and distinguishes from siblings 'list-rolltables' (summary only) and 'roll-on-table' (random draw). It clearly states what the tool does.

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 positions the tool as 'the deterministic way to inspect or audit' and contrasts with alternative tools ('list-rolltables' gives summary, 'roll-on-table' draws random). It also specifies resolution by 'id or exact name'. Lacks explicit 'when not to use', but the contrast is sufficient.

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