streamdeck_delete_page

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

With no annotations, the description carries the full burden, but it only states the action. It does not disclose irreversibility, side effects on the profile, behavior when page_index is invalid, or whether confirmation is needed.

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?

It is a single, direct sentence with no redundant filler and identifies the core operation early. However, its brevity borders on underspecification, so not a 5.

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 destructive tool with no annotations, no output schema, zero parameter descriptions, and four optional identifier fields, this description is inadequate. It does not specify which parameter is required, what happens after deletion, or how the target page is resolved.

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 description coverage is 0% and the description adds no parameter information. It does not explain how the four all-optional properties relate (page_index vs profile_id/profile_name/directory_id), which is critical for choosing the correct identifier.

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 names the action (delete) and the object (page from a Stream Deck profile), making it distinct from siblings that read or write pages. It does not add scope detail such as which profile or how the page is identified, but the core purpose is unambiguous.

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 when-to-use or exclusionary guidance is provided. An agent must infer from the verb 'Delete' that this is for removing pages, and there is no comparison with streamdeck_manage_profile or streamdeck_write_page.

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