get_hashtag_info

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

With no annotations, the description must fully disclose behavioral traits. It only states 'get metadata', implying a read operation, but fails to mention auth requirements, rate limits, or the nature of the metadata returned. Insufficient transparency.

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, concise sentence with no fluff. While it lacks detail, it is not verbose. It could be expanded slightly (e.g., 'including post count and top media') while remaining concise.

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 presence of an output schema, the description should summarize what metadata is returned (e.g., post count, top posts). It does not. The tool is one of many get_* siblings, yet no differentiation is offered, making the description incomplete for effective use.

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%, requiring the description to compensate. The description does not explain the 'name' parameter beyond the obvious; the tool name and parameter name alone provide minimal context. Adding a brief elaboration (e.g., 'name is the hashtag text') would have raised the score.

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 clearly states the tool retrieves metadata for an Instagram hashtag, using a specific verb and resource. Among many sibling tools focused on specific entities (e.g., reels, locations), this tool is uniquely identifiable for hashtag metadata.

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 like get_hashtag_reels or search_instagram. Missing context on prerequisites or limitations, leaving the agent without usage direction.

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