foundry_list_rolls

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

The readOnlyHint annotation already covers safety, and the description's 'recent' adds temporal ordering. However, it doesn't disclose behaviors like pagination, default limits, or response format. The 'Get' action is consistent with the annotation, and no contradiction exists.

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 extremely concise—a single five-word sentence with no wasted words. It lacks detail, but for what it conveys, it is well-structured and front-loaded.

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?

With no output schema and a terse description, the agent gets no information about return shape, what constitutes a 'roll', or how this differs from related tools. The absence of usage and behavioral context leaves significant gaps.

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 description offers no parameter explanations. Schema coverage is 67% (userId and clientId have descriptions), but 'limit' lacks any description and the tool description does not compensate. Parameter names are intuitive but not sufficiently clarified.

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 'Get recent rolls' clearly specifies the action (get) and resource (rolls), with 'recent' indicating plural temporal retrieval. It does not explicitly differentiate from sibling tools like foundry_get_last_roll or foundry_roll, so it misses the top score.

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?

There is no guidance on when to use this tool versus alternatives such as foundry_get_last_roll or foundry_roll. No context is given for typical usage scenarios, exclusions, or requirements.

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