create_page

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

No annotations are provided, so the description carries the full disclosure burden. It discloses the default published state (draft unless published=True), which is a useful behavioral detail. However, it does not mention permissions, potential failures, or that it creates a new resource (though that is implied by 'Create').

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 sentence that gets to the point immediately. It front-loads the core purpose and includes the key default behavior without any fluff.

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 schema defines required parameters and the output schema exists, the description is minimal but sufficient for a simple create action. However, it does not mention that the page is created within a course or any prerequisites. It is adequate but leaves some context to the agent's inference.

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 schema has 0% description coverage and the description adds minimal parameter semantics. It only clarifies the default for 'published' (as draft), but does not explain 'course_identifier', 'title', or 'body'. The schema itself provides defaults but no meaning, so the description should compensate but does not.

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 the action ('Create') and the resource ('wiki page'), which distinguishes it from read or update tools like get_page_content or edit_page_content. It does not explicitly compare with sibling creation tools, but the resource type is unambiguous.

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 provides no guidance on when to use this tool instead of alternatives like edit_page_content or update_page_settings. An agent must infer from the name that this creates a new page rather than modifying an existing one. No exclusions or conditions are given.

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