instagram_search

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new context: it discloses the credit cost (1 credit) and describes the shape of the results (accounts, hashtags with post counts, places with location ids), which matters given there is no output schema.

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?

Two short sentences, zero waste: the capability is front-loaded and the cost is separated onto its own line. Every sentence 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?

For a one-parameter search tool with no output schema, the description covers the entity scope, result contents, and cost, and annotations cover the safety profile. Minor omissions remain, such as result limits or pagination behavior, but nothing essential to correct invocation is missing.

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 100% for the single parameter, so the schema already documents 'q' as the search text with a max length and example. The description adds only that the text is matched against accounts, hashtags, and places, which is mild added meaning. Baseline 3 applies.

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 (Search) and the three resource types it covers (accounts, hashtags, places), which distinguishes it from single-entity siblings like instagram_username, instagram_hashtag, and instagram_place. It does not explicitly differentiate from other search-style siblings such as instagram_reels_search or instagram_audio_search, but the multi-entity scope is clear.

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 when-to-use guidance or routing to alternatives is given. An agent must infer on its own whether to use this multi-entity search or a targeted lookup like instagram_username. The only practical guidance is the cost line, which is a budgeting note rather than usage direction.

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