list_creatures

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

No annotations are present, so the description must fully disclose behavior. It does not state whether the operation is read-only, whether it requires a campaign context, that results are paginated via the page parameter, or what the response shape is. The description adds no behavioral insight beyond the name itself.

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 short, but this is under-specification rather than conciseness. 'List creatures' adds no information beyond the tool name and does not front-load any useful detail. Every sentence should earn its place; this phrase does not.

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 two parameters and no annotations or output schema, the description must carry the contextual burden. It does not mention the required campaignId, pagination behavior, or the scope of creatures returned. An agent cannot reliably select or invoke this tool correctly based on the description alone.

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 0%, so neither the schema nor the description explains the parameters. The description does not clarify that campaignId likely scopes the listing or that page controls pagination. With two parameters completely undocumented, the description fails to compensate.

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 'List creatures' is a near-verbatim restatement of the tool name. It states a generic verb and resource but provides no scope, filtering criteria, or relationship to the required campaignId parameter. It does not distinguish list_creatures from the many sibling list_* tools beyond the resource name.

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?

No guidance is provided about when to use this tool versus get_creature, list_characters, or search. There is no mention of prerequisites, such as needing a campaignId, nor any context for when listing creatures is appropriate. The agent is left without direction.

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