create_page

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

Annotations provide destructiveHint=true and openWorldHint=true. The description calls it a 'create' action, which aligns with openWorldHint but may contradict destructiveHint (creation is typically non-destructive). Beyond that, no additional behavioral traits like permissions, rate limits, or side effects are disclosed.

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—concise and to the point. No unnecessary words, but it is slightly terse and could benefit from a brief example or additional context without becoming verbose.

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 description is minimal, lacking details on return values, error conditions, or behavior after creation. With no output schema and moderate complexity (5 params, 2 required), the tool description should provide more context to guide the agent, especially given the lack of output schema.

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 100%, so all five parameters have descriptions in the schema. The description adds no extra meaning beyond the schema's parameter details, earning a baseline of 3.

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 'Create a new wiki page in a course,' specifying the verb, resource, and context. It differentiates from sibling tools like create_assignment or create_discussion, though it does not explicitly contrast with similar create tools like create_module_item.

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 when to use the tool (to create a wiki page) but provides no guidance on when not to use it or mention of alternatives among the many sibling tools. No explicit usage context or exclusions are given.

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