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

With no annotations, the description carries the full disclosure burden. It adds billing cost ('Billing per call: 1 Credits') but omits output format, pagination, result limits, or the meaning of locationId values. The read-only behavior is only implied by the verb 'Get'.

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 focused sentence plus a concise billing note. There is no filler, redundancy, or irrelevant detail.

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 tool has a simple schema, but the lack of an output schema and annotations raises the description's burden. The description fails to mention return format, whether trends are returned as a list, or how locationId should be resolved. It is enough for a basic call, but not for robust agent decision-making.

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 0%, so the description must compensate for the undocumented locationId parameter. The phrase 'worldwide or a specific region' gives a hint about the parameter's purpose, but it does not specify valid values, the worldwide value, or how to discover region IDs. This is insufficient for a completely undocumented parameter.

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 the exact action ('Get twitter trends') and the scope ('worldwide or a specific region'), pairing a specific verb with a clear resource. It is also distinct among the sibling tools, as it is the only trends-specific tool.

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 provided on when to use this tool versus alternatives, nor are prerequisites mentioned. The description does not reference get_misc_locations for looking up location IDs, nor does it explain how to specify worldwide versus a specific region.

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