notion_trash_page

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

No annotations provided, so the description carries full burden. It only mentions routing infrastructure and does not disclose any behavioral traits (e.g., destructiveness, reversibility, required permissions).

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?

Description is short but front-loaded with routing details that are not core to purpose. It could be more concise by omitting infrastructure information and focusing on behavior.

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 only one parameter and an output schema, the description still fails to explain what the tool does, expected arguments, or return behavior. It is insufficient for an AI agent to use correctly.

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 has 0% coverage for parameter descriptions. The description adds minimal value by stating the 'arguments' parameter is a JSON string, but does not specify expected contents (e.g., page_id) or structure.

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?

Description states it is a 'trash_page' operation, which implies moving a page to trash, but does not explicitly clarify what trashing entails. Among sibling tools like 'notion_archive_page', the description lacks differentiation. It merely restates the name and adds routing details.

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 on when to use this tool versus alternatives such as 'notion_archive_page' or 'notion_delete_block'. The description does not mention context, prerequisites, or scenarios.

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