Create Page

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

Annotations already declare destructiveHint and openWorldHint, so the agent knows that this is not a read-only, fully predictable operation. The description adds no further behavioral context such as whether creation overwrites an existing page by title, how publishing defaults work, or what permissions are required. It merely re-states the create action without enriching the 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 a single, focused sentence with no filler. It front-loads the verb and object and states the course scope without adding redundant detail.

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?

The output schema exists so return values do not need to be explained, and the input schema already documents all parameters fully. The description would ideally offer a note about page title collisions or publishing defaults, but for a basic CRUD tool this remains sufficient for many an agent to 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?

The input schema covers all 5 parameters with descriptions, including the HTML body, publisher, and editing roles, so the schema already carries the parameter load. The description does not add anything beyond the natural notion that the page belongs to a course, which was move the schema baseline of 3 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?

The description uses a specific verb ('Create') and resource ('new wiki page in a course'), making the primary action immediately recognizable. It also distinguishes this tool from siblings like update_page, delete_page, and get_page, which an agent could otherwise confuse with it by name alone.

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 word 'new' implicitly signals that this is for creating pages rather than updating existing ones, so some usage context is present. However, there is no explicit guidance about when to prefer this over update_page, nor mention of any exclusions or preconditions.

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