List Stat Blocks

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds useful context about the return content (ordered procedure summaries, retained text-only entries) and the caveat about executability across workflows, which goes beyond 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, efficient and front-loaded with the main purpose. The caveat sentence adds important context without excessive verbosity. Slightly more could be said about use cases, but it remains compact.

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's simplicity (no parameters) and the output schema providing return structure, the description covers all necessary aspects: what items are listed, their attributes, and a critical caveat about executability. It's complete for an agent to decide 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?

With zero parameters, the schema provides no parameter information, so the description's detailed listing of what the tool returns serves as the semantic content. This fully compensates for the absence of parameters, providing clear expectations.

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 it lists every installed redistributable SRD Stat Block with specific attributes (ids, names, summaries, attacks, defenses, damage modifiers). It distinguishes itself from siblings like list_catalog_units and inspect_catalog_unit by focusing on stat blocks specifically.

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 implies its use for discovering available stat blocks before selecting one, but it doesn't explicitly address when not to use it or which sibling to prefer. The phrase 'Catalog presence does not imply executable' adds caution, providing some guidance on interpretation.

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