blogger_pages_delete

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

With no annotations provided, the description carries the full burden. 'Permanently delete' discloses the destructive and irreversible nature of the operation, which is valuable. However, it omits other behavioral context such as permission requirements, behavior on non-existent page, or whether the operation is idempotent.

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 of 8 words. It uses a strong verb and directly states the action and target, with zero wasted words.

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 simple delete tool with no output schema and complete parameters, the description covers the essential purpose but lacks contextual richness. It does not mention prerequisites, return behavior, or broader impact beyond the page itself. Adequate but minimal.

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%, covering both blogId and pageId. The description adds minimal semantic value beyond the schema—'by its ID' reinforces pageId's role but does not explain blogId's scoping purpose. Baseline 3 is appropriate when the schema already documents parameters.

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 'Permanently delete a static page by its ID' uses a specific verb ('delete'), identifies the resource ('static page'), and specifies the mechanism ('by its ID'). This clearly distinguishes it from sibling tools like blogger_posts_delete and blogger_comments_delete.

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 usage for static page deletion through the phrase 'static page', but it does not explicitly contrast with alternatives (e.g., 'use blogger_posts_delete for posts') or state any exclusions. The sibling awareness is present but not explicitly leveraged to guide selection.

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