add_page

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

No annotations are provided, so the description carries the full responsibility for behavioral disclosure. It only states the action without mentioning side effects such as file modification, prerequisites like the file existing, or behavior on duplicate page names, leaving significant ambiguity.

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, direct sentence with no filler, front-loaded with the verb 'Add'. It is as concise as possible while communicating the core purpose.

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?

For a tool with no output schema and no annotations, the description omits return behavior, error conditions, and side effects. This makes it under-specified for an agent to fully understand the tool's impact, though the simple purpose is clear.

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 already documents both filePath and pageName with 100% coverage, so the description adds no additional parameter semantics. It doesn't clarify path formats or naming constraints, but the schema provides basic definitions, placing this at the baseline.

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 'Add a new page (tab) to a draw.io diagram' uses a specific verb and resource, clearly distinguishing it from sibling tools like add_node and add_edge. The mention of 'page (tab)' clarifies the target object and differentiates this from tools that operate within a page.

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 the tool is for adding a new tab to an existing diagram, but it does not explicitly state when to use it over alternatives like create_diagram. No exclusions or conditions are provided, leaving the agent to infer context from the tool name and schema.

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