search_hashtag

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

No annotations are provided, so the description must carry the behavioral burden. It does convey that this is a resolution/lookup operation, not a mutation. However, it does not mention authentication needs, error conditions, rate limits, or what happens when the hashtag is not found, which would be useful given zero annotation support.

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?

One tight sentence with no filler. The key purpose is front-loaded, and the workflow dependency is placed at the end as supporting context. Every word earns 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?

The tool is simple and has an output schema, so the description need not restate return values. However, the unexplained optional 'account' parameter and the absence of any behavioral caveats leave the description slightly incomplete for an agent deciding how to call this tool correctly.

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 explain the parameters. It only clarifies that 'hashtag' is the hashtag name, but the optional 'account' parameter is completely unexplained. This is a meaningful gap because the agent cannot infer when or why to provide an account.

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 precise verb ('Resolve'), the resource ('hashtag name'), and the result ('Graph id'), and even places it in a workflow ('needed before get_hashtag_media'). This clearly differentiates it from sibling tools like get_hashtag_media or get_mentions.

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 explicitly says the tool is needed before get_hashtag_media, giving a concrete usage context. It does not enumerate when not to use it or discuss alternatives, but the workflow dependency is strong, actionable guidance.

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