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

No annotations are present, and the description does not disclose whether the tool is read-only, any side effects, cost implications (though it mentions billing per call, which is not a behavioral transparency detail), or error patterns. The lack of annotation means the description should have provided this, but it didn't.

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 concise but includes an irrelevant billing note ('Billing per call: 1 Credits') that detracts from clarity. Structurally it's a single sentence, but the extra billing info is unnecessary for tool usage.

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 description lacks essential context: output format, pagination usage, parameter relationships, and any prerequisites. With no output schema, the description should have explained what the tool returns, but it doesn't. This leaves the agent uncertain about how to interpret results.

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?

The schema includes descriptions for all four parameters, but they are vague and potentially confusing. 'tabs' lists valid values; 'hashtag' is just the name; 'next_page' and 'next_max_id' have overlapping and unclear statements. The descriptions do not adequately clarify the parameters' roles.

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 it searches by hashtag on Instagram, which is specific and distinguishes it from sibling tools that search by other criteria. However, it does not mention what the search returns (e.g., post list, metadata), so it's not fully explicit.

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 how to handle pagination with next_page and next_max_id. The description is minimal and offers no usage context.

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