Remove a registered app

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

The description claims the tool 'delete's' an app alias, which implies destructive behavior. However, annotations have destructiveHint: false, indicating the tool is not considered destructive. This contradiction is critical. No additional behavioral context (e.g., permission requirements, irreversibility) is provided beyond the annotation mismatch.

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 extremely concise: two sentences that front-load the main action and quickly list arguments and return value. No extraneous 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 2-parameter tool without an output schema, the description covers the core action and return format. It could mention error behavior (e.g., what if alias does not exist) or dependencies, but overall it is fairly complete and usable.

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 schema already describes both parameters with 100% coverage. The description adds value by specifying the return structure '{ alias, removed }', which is not present in the schema. It also clarifies the purpose of alias as removing both the alias and its stored token, adding context beyond the schema's 'Alias to remove.'

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 'Delete an app alias (and its stored token) from the registry', using the specific verb 'delete' and identifying the resource as an app alias. This distinguishes it from sibling tools like 'singular_register_app' (create) and 'singular_list_apps' (list).

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 does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. However, the action is clear: if the goal is to delete an app alias, this is the tool. It lacks guidance on when not to use it or what to do instead (e.g., update).

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