unfollow_topic

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

The description provides no details about behavioral traits such as side effects (e.g., does it update my followers list?), authentication requirements, or rate limits. With no annotations, the description should compensate but fails to do so.

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 very concise at one sentence. While it is not verbose, it could be slightly expanded to include usage context without becoming wasteful.

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 simplicity of the tool (one parameter, no nested objects, output schema exists), the description is minimally adequate but lacks context about preconditions or what happens after unfollowing. It does not leverage the fact that an output schema exists to mention return values.

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 covers the single parameter 'topic_id' with a description, achieving 100% coverage. The tool description does not add any extra meaning beyond the schema, so baseline score of 3 is appropriate.

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 'Unfollow a topic on X/Twitter' clearly states the action (unfollow) and the resource (topic), distinguishing it from the sibling tool 'follow_topic'.

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 on when to use this tool versus alternatives. For example, it does not mention prerequisites like being already following the topic, or when to use other tools like 'follow_topic' or topic search tools.

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