demo_remove

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

With no annotations, the description carries the full behavioral burden, but it only states that something is removed. It does not disclose whether the removal is permanent, whether it affects user data, or what side effects occur, which is especially important for a destructive zero-parameter operation.

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 short sentence with no filler; the action is stated up front. For such a simple zero-argument tool, this level of conciseness is appropriate despite the semantic ambiguity.

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?

Given the low complexity, one sentence might seem sufficient, but the absence of any context about when to run this cleanup, whether it is safe, and what happens to the vault means an agent cannot confidently select and invoke it. The output schema exists, so return values are not the gap; usage and side-effect context are.

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 zero properties and 100% coverage, so no parameter documentation is needed. The description's reference to removing the demo visit implies the operation requires no user input, matching the empty schema; baseline for zero parameters is appropriate.

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 says 'Retire la visite demo du vault' (removes the demo visit from the vault), giving a verb and a resource, so it is not a tautology. However, 'visite demo' is ambiguous and the definition does not clarify what a demo visit is or how it differs from other removal tools such as delete_note or empty_trash.

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?

There is no guidance about when to call this tool versus alternatives. A sibling tool named demo_generate strongly suggests a counterpart, but the description never says 'use after demo_generate' or 'use to clean up demo data', so the agent is left to infer usage.

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