Delete Page

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

Annotations already declare destructiveHint=true, so the agent knows the tool is destructive. The description adds no additional behavioral context (e.g., whether page numbers shift, if transcripts are also deleted, or if the operation is irreversible). It merely restates the action.

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 one sentence with no extraneous words. It is front-loaded with the purpose. Every word earns its place.

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 lacks context about return values (no output schema), side effects (e.g., impact on document structure), prerequisites (e.g., permissions), and error cases. For a simple delete operation, more completeness is expected.

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 100%, with each parameter having a description (collId, id, page). The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the schema carries the descriptive burden.

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 'Delete a page from a document.' uses a specific verb ('Delete') and clearly identifies the resource ('a page from a document'). It distinguishes this tool from sibling tools such as transkribus_page_add (add a page) and transkribus_page_move (move 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 provides no guidance on when to use this tool versus alternatives, such as when not to use it (e.g., for hiding a page) or any prerequisites. No mention of alternatives like transkribus_page_replace or transkribus_page_update_hide_on_sites.

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