ig_search_hashtag

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

With no annotations, the description carries the full burden. It discloses the rate limiting behavior (30 per 7 days) and implies the tool is a non-destructive read operation. However, it does not specify what is returned on success or error, leaving some behavioral uncertainty.

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 three short sentences: core purpose, prerequisite context, and constraint. It is front-loaded and every sentence adds unique value with no redundancy.

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?

For a simple lookup tool with one parameter and no output schema, the description is nearly complete. It explains the role in the tool sequence and the rate limit. Minor omission: it could briefly mention the return format (e.g., 'returns a hashtag ID'), but this is 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 100% and the description adds the nuance that the parameter should be provided 'without #'. This adds meaningful guidance beyond the schema's basic description 'Hashtag name to search'.

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 action (search) and resource (hashtag ID), and explicitly distinguishes it from siblings by stating it is required before querying hashtag media. The verb 'Search' and noun 'hashtag ID' are specific and unambiguous.

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 provides explicit context: 'Required before querying hashtag media' and a usage limit 'Limited to 30 unique hashtags per 7-day rolling window.' This helps the agent understand when to use the tool and constraints. It does not explicitly mention alternatives or when not to use, but the context is sufficient for this simple tool.

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