Notifications_getDestinations

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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'Returns' but does not explicitly state that the operation is read-only, nor does it mention pagination, authentication, rate limits, or response format. The 'Runs in your Kuudo deployment' note adds some context, but 'Catalog entry' is vague and potentially misleading.

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 short, but the core purpose sentence is placed last, after 'Catalog entry' and the deployment note. The phrase 'Catalog entry' does not earn its place and adds noise rather than clarity.

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?

With no output schema, the description should explain what 'information about destinations' includes, but it does not. The deployment caveat is useful, but the description omits what a destination is, the shape of the returned data, and any potential limitations or error conditions.

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 parameters and the description correctly makes no parameter claims. The 100% schema coverage baseline applies, and the description adds no unnecessary parameter information.

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 tool returns information about all destinations, and the word 'all' distinguishes it from the singular getDestination sibling. However, the opening phrase 'Catalog entry' is confusing and the description does not define what a destination is in this context.

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?

There is no guidance on when to use this tool versus alternatives like getDestination or createDestination. The deployment note about running in Kuudo is environmental context, not selection guidance.

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