request-roll

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

No annotations provided, so description carries full burden. Discloses it posts a card using dnd5e inline roll enricher, that players click to roll their own check. Does not detail what happens after clicking, error handling, or the resulting message format. Adequate but not exhaustive.

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 purpose, no extraneous information. Every sentence earns its place. Efficient and clear.

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 6 parameters, no output schema, and no annotations, the description covers the core functionality (posting a request card). Lacks details on return value or error cases, but the tool's simplicity and clear use case compensate. Sufficient for an agent to select and invoke 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 100% and each parameter is already well-described in the schema (e.g., ability, skill, kind, dc). Description adds context about dnd5e enricher and GM-only but does not provide additional meaning beyond schema for parameters. 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?

Description clearly states it posts a click-to-roll request card for saving throws, ability checks, or skills. Distinguishes from siblings like 'roll-on-table' (table rolling) and 'send-chat-message' (generic message) by specifying it's a table-facing prompt for players to roll their own checks.

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?

Explicitly says GM-only, indicating it's for GMs to prompt players. Implicitly for group challenges where each player rolls individually, but does not explicitly state when not to use or mention alternatives like 'send-chat-message' for custom messages.

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