pbi_delete_bookmark

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

Beyond the annotations that declare destructiveHint=true, the description adds the crucial requirement 'confirm=true' to actually execute the deletion. It also mentions the side effect of removing the bookmark from the index, providing useful behavioral context beyond the structured metadata.

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 two short sentences, front-loads the verb and resource, and wastes no words. It efficiently conveys the action, the index side effect, and the destructive confirmation requirement.

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 an output schema and annotations, the description is mostly complete. It warns about destructiveness and the confirm flag, but does not mention failure scenarios (e.g., bookmark not found) or what happens if confirm is false. Acceptable for simple tool.

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?

With 0% schema description coverage, the description carries the burden of explaining parameters. It explains that 'confirm' must be true for deletion, and 'name' is implicitly the bookmark to delete, but 'request_id' remains undocumented. Partial compensation, but not complete.

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 'Borra un marcador' (deletes a bookmark) and specifies the additional behavior 'lo quita del indice' (removes it from the index). This distinguishes it from sibling tools like pbi_create_bookmark or pbi_list_bookmarks.

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 (when you want to delete a bookmark) but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The destructive warning hints at caution but does not elaborate on when to avoid use.

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