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

Annotations already establish that this is a non-read, non-destructive, open-world operation. The description adds useful behavioral details beyond that: required fields (adventureId, name), the tags array for filterability, and the automatic addition of documentType to the searchable keyword set. It does not address auth or side effects, but it goes well beyond what annotations alone provide.

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 efficiently structured and front-loaded with the action and required fields. The list of valid documentType values is lengthy but necessary, and every sentence adds operational value. A slight tightening could combine the use-case and negative-guidance sentences, but there is no wasted content.

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 empty schema, the description covers all core invocation concerns: required parameters, valid enum values, intended use cases, excluded page types, and the tagging/keyword behavior. With an output schema presentatoire, the absence of return-value detail is not a gap. The agent can select and call this tool correctly based solely on the description.

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 input schema is empty, so the description is the only source of parameter knowledge. It compensates fully by naming the required parameters (adventureId, name), enumerating valid documentType values, explaining the tags array use, and explicitly excluding items/rules as page types. This gives the agent everything it needs to construct a valid call despite the empty schema.

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 states a specific verb and resource: 'Create a new page inside an adventure.' It also lists concrete use cases (scene descriptions, encounter rooms, NPC profiles, plot beats) that distinguish it from related tools like world-page creation. The negative guidance about items and rules further disambiguates the tool's scope.

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 says when to use this tool ('Use this for scene descriptions, encounter rooms, NPC profiles, plot beats') and when not to ('Items and rules are NOT page types'). It names the alternative approach: author those in the vault and reference them, not as adventure pages. This gives the agent clear routing guidance without needing to inspect other tools.

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