topics_unsubscribe

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

No annotations are provided, so the description must disclose behavioral traits. The description only says 'Remove a subscription.' It does not mention that this action is irreversible, what permissions are required (e.g., topic owner), or any side effects (e.g., messages will no longer be delivered). The output schema exists but is not referenced. This is insufficient for a mutation tool.

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 a single sentence of three words: 'Remove a subscription.' It is extremely concise and front-loaded, with every word contributing to the purpose. No unnecessary information is present.

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?

Given the tool's low complexity (two parameters, one required, simple action) and the presence of a complete input schema and output schema, the description is minimally adequate. However, it lacks context about the source of the subscription ARN and the permanence of the action, which would be helpful for an agent. A more complete description would add 'Removes a subscription from a topic permanently.'

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?

Schema description coverage is 100%, so the baseline is 3. The schema already describes 'subscription_arn' as 'The subscription ARN (from list_subscriptions).' and 'region' as 'Region such as fr-par. Defaults to the configured region.' The description adds no additional semantic value beyond the schema.

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 'Remove a subscription.' clearly identifies the action (remove) and the resource (subscription). In the context of sibling tools like topics_subscribe and topics_list_subscriptions, it's reasonable to infer this is about removing a subscription from a topic. However, it does not explicitly mention 'topic' or the broader context, which would improve clarity.

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 provides no guidance on when to use this tool versus alternatives. Siblings include topics_subscribe (to add subscriptions) and topics_list_subscriptions (to find subscription ARNs), but the description does not indicate that this tool should be used to unsubscribe or that the subscription ARN should come from list_subscriptions (though the schema hints at it). No when-not-to-use or exclusion logic is given.

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