Search a hashtag

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

Goes well beyond the readOnly/idempotent/destructive annotations by disclosing Meta's hard limit of 30 unique hashtags per 7 days per account and the requirement for a Facebook Login token with Instagram Public Content Access. These are exactly the constraints an agent needs before invoking and are not expressible in annotations.

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?

Three tight sentences: purpose and modes first, then operational constraints, then a concrete example. No filler, and the most decision-relevant information (the two modes) is front-loaded.

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?

Covers purpose, modes, auth prerequisites, rate limits and an example, which is substantial for a 4-parameter read tool with no output schema. It does not clarify what a result looks like (e.g. media items, pagination) or the meaning of 'limit', leaving a small gap.

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 coverage is 50%: 'hashtag' and 'response_format' are documented in the schema while 'kind' and 'limit' are not. The description fills the most important gap by defining 'kind' as 'top' vs 'recent (last 24 hours only)'; 'limit' remains only inferable from its 1-50 bounds.

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?

States a specific verb and resource ('Find public posts for a hashtag') and immediately qualifies the two modes ('top' most popular vs 'recent' last 24 hours). It is unambiguous what the tool does, though it makes no reference to any sibling tool since none of them overlap in function.

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 example ('What's trending under #punefood?') anchors a concrete use case, and the top/recent distinction tells the agent which mode fits which intent. There are no explicit exclusions or named alternatives, but the surrounding siblings are messaging/media tools that don't compete, so context is clear.

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