Удалить страницу

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

The description includes a key behavioral detail: the page is moved to trash rather than permanently deleted. This adds value beyond a simple 'delete' statement. However, no further behaviors (e.g., permissions, side effects) are disclosed, but given no annotations, this is good.

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, well-structured sentence that conveys the essential purpose and behavior without any extraneous content. It is appropriately sized and front-loaded.

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 operation with one parameter and no output schema, the description is fairly complete. It states the action and a key behavior (trash). Minor omissions like prerequisites or error scenarios are acceptable for this complexity level.

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 has 100% coverage for the only parameter (id), describing it as 'ID страницы'. The description adds no further semantics beyond what the schema already provides, so baseline score of 3 applies.

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 action (deletes a page) and resource (page), with additional behavioral detail (moves to trash). This distinguishes it from sibling tools like create, update, or add comment.

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 explicit guidance on when to use this tool versus alternatives. Usage is implied from the description, but no when-not-to-use conditions or comparisons with siblings (e.g., permanent deletion) are provided.

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