Delete a saved screen

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

Annotations already declare the tool as destructive and idempotent, so the description does not need to repeat those traits. It adds meaningful behavioral context by disclosing that the deletion is scoped to screens saved through this server and does not affect Chrome extension screens.

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 action and scope, and contains no redundant or filler text. Every sentence adds useful information.

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 one-parameter delete tool with rich annotations but no output schema, the description covers the key scope limitation. It is still incomplete regarding how the 'name' parameter identifies the screen and what happens on failed deletion, which are relevant for an agent invoking a destructive operation.

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 0% description coverage, and the description provides no information about the required 'name' parameter, such as whether it must match exactly, is case-sensitive, or how missing screens are handled. With one undocumented parameter, the description does not compensate for the schema gap.

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 states a specific verb and resource: 'Delete a screen saved through this server.' It also clarifies that Chrome extension screens are out of scope, making the operation distinct, though it does not explicitly name sibling tools such as save_screen or list_saved_screens.

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 when to use it by restricting deletion to screens saved through this server and noting that Chrome extension screens are unaffected. However, it does not explicitly state when to choose this over alternatives or mention prerequisites such as confirmation or exact matching.

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