page_delete

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

The description mentions deletion and unregistering, but given no annotations, it fails to disclose irreversibility, cascading effects, permission requirements, or whether dryRun is available. Behavioral transparency is insufficient for a deletion tool.

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 very short (one sentence), which saves token space. However, it sacrifices important details. It is not optimally concise because it lacks necessary information, earning a middle 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?

With no output schema and 3 undocumented parameters, the description is incomplete. It does not cover return values, side effects, or error conditions. For a deletion tool, more completeness is needed.

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 coverage is 0%; the description adds no parameter explanations beyond what their names imply. For example, it does not describe projectPath, pageName, or the effect of dryRun=true. This leaves agents to guess parameter semantics.

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 'delete' and resource 'page folder' with the additional action 'unregister it from pages.json'. It unambiguously identifies the tool's function and is distinct from sibling tools like page_add or page_duplicate.

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 alternatives, prerequisites (e.g., page emptiness), or when not to use it. For a destructive action like deletion, such context is critical.

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