Notifications_deleteDestination

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does indicate the operation is destructive by saying 'Deletes,' and it adds an odd note that the tool 'runs in your Kuudo deployment, not here.' But it does not explain irreversibility, permissions, side effects, or what executing 'not here' means for the agent.

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 only two sentences and wastes very few words. The core action is stated near the end, after the unusual 'Catalog entry' and environment statements, but overall it is compact and easy to scan.

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 delete operation with no annotations, no output schema, and empty input schema, the description is too thin. It fails to explain how the destination is specified, what happens upon deletion, whether the action is reversible, or what environmental caveat 'not here' actually implies for invocation.

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 zero documented properties and allows additional properties, so there is no structural parameter information. The description says 'that you specify' but never names the expected identifier or format, which is a meaningful gap. The 0-param baseline helps, but the phrase implies a required destination reference that is left undefined.

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: 'Deletes the destination that you specify.' This distinguishes it from subscription-related siblings like deleteSubscriptionById. However, the opening 'Catalog entry. Runs in your Kuudo deployment, not here' adds an execution-environment caveat that muddies the clarity slightly.

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 the tool is used when deleting a destination, but provides no guidance on when to use it versus alternatives, no prerequisites, and no mention of obtaining the destination identifier first. There is no when-not-to-use guidance, leaving the agent to infer usage entirely.

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