add_page

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

No annotations are provided, so the description carries full burden. It discloses that the new page is selected, but fails to mention whether a document must already be open, potential errors on duplicate names, or the fact that this is a mutating operation (though 'Add' implies it).

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, front-loaded sentence that is clear and free of fluff. It is appropriately concise for the tool's simplicity, but misses parameter and usage details. This is not a padded description, so it earns a high conciseness score.

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 tool has a simple one-parameter schema but no annotations. The description covers the core action but is missing essential context about prerequisites (e.g., an open document) and parameter meaning. It is insufficient for an agent to reliably invoke the tool without guesswork.

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 defines a single required parameter 'name' with no description, and schema description coverage is 0%. The description does not explain the meaning or format of 'name', leaving it completely undocumented.

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 verb 'Add' and resource 'page', and also specifies a secondary behavior 'select it'. This distinguishes it from siblings like select_page (which only selects) and new_document (which creates a document, not 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?

No guidance is provided on when to use this tool versus opening/creating a document first. It does not mention prerequisites such as an open document, nor does it reference any alternatives or exclusions.

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