apex_delete_button

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

Annotations already declare destructiveHint=true, and the description merely repeats the delete action without adding extra behavioral context (e.g., permanence, cascading effects, permissions required). It does not contradict annotations, but adds no value beyond them.

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, front-loaded sentence that states the action and target without redundancy. It is efficient and avoids unnecessary elaboration.

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 tool is a simple delete operation with fully documented parameters, an output schema, and annotations indicating destructive behavior. The one-line description is sufficient given the structured metadata; no critical information is missing. Minor gap: it doesn't state whether the button must exist or if deletion is idempotent, but annotations imply non-idempotency.

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 clearly described (app_id, page_id, button_name). The description doesn't add any parameter-specific information, but the baseline of 3 is appropriate since the schema already carries the full semantic 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 button from an existing app.' uses a specific verb (delete) and resource (button), clearly distinguishing this from sibling tools like apex_delete_region or apex_delete_item. The phrase 'from an existing app' establishes the operational context cleanly.

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, nor any exclusions or prerequisites. It simply states the action without explaining when a user should choose this over other delete tools (e.g., when a button exists) or mention that the button must already be present.

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