Notifications_getSubscriptionById

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

No annotations are provided, so the description carries the full burden. It discloses only that the tool runs remotely and returns subscription information, but says nothing about authentication, required identifiers, error behavior, or response shape. The opening 'Catalog entry' is also unclear.

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 brief, but the first two sentences are peripheral context rather than core semantics. The actual purpose is delayed to the final sentence, and 'Catalog entry' adds noise without earning its place.

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 and no annotations, the description should explain return values and invocation requirements. It only vaguely says 'Returns information' and never clarifies the subscription ID parameter or distinguishes itself from the very similar getSubscription sibling. Insufficient for reliable selection and 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 no properties and allows additional properties, so the description is the only source of parameter meaning. It mentions a notification type but does not name the parameter, does not mention subscriptionId, and gives no formats—making correct invocation unlikely for a get-by-id operation.

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 clear action ('Returns information about a subscription') and a resource ('the specified notification type'). However, it omits the 'by ID' aspect and could equally describe the sibling Notifications_getSubscription, so it lacks sibling differentiation.

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 guidance is given about when to use this tool versus alternatives. The phrase 'Runs in your Kuudo deployment, not here' is an environment note, not a selection criterion, so an agent gets no help choosing between getSubscriptionById and getSubscription.

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