Notifications_getDestination

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 mentions the tool runs in the user's Kuundo deployment rather than here, which is useful, but it does not state whether this is read-only, what authentication is required, or what side effects may occur. 'Catalog entry' is also unexplained.

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 and mostly concise, but 'Catalog entry' is an unclear and expendable opening. The sentence about running in the Kuundo deployment is relevant but phrased informally. Overall, the structure is acceptable but not tightly purposeful.

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?

The description lacks essential invocation details: how to specify the destination, what kind of information is returned, what 'Catalog entry' means, and when this tool should be used. With no output schema and no annotations, the description is not sufficient for an agent to confidently invoke the tool.

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 declares zero properties but allows additionalProperties, while the description says 'the destination that you specify.' This implies a destination parameter exists, but the description never names it or explains its format. The schema cannot guide invocation, so the description fails to bridge that 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 that the tool 'Returns information about the destination that you specify,' which gives a clear verb and resource. However, the phrase 'Catalog entry' adds confusion, and the description does not differentiate this from the sibling tool Notifications_getDestinations beyond the singular form.

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 such as Notifications_getDestinations or Notifications_createDestination. The note about running in the user's Kuundo deployment is contextual but does not explain selection criteria or exclusions.

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