ig_business_discovery

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

With no annotations, the description discloses some useful behavior by specifying that it returns public info for Business/Creator accounts, which implies a read-only lookup with limited scope. However, it does not mention auth requirements, rate limits, or how private/nonexistent accounts are handled.

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?

It is a single, front-loaded sentence with no wasted words. The key scoping detail ('another account') appears immediately.

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 two-parameter lookup with full schema coverage and no output schema, the description is nearly sufficient. It could be slightly more complete by clarifying error behavior for private or non-Business accounts.

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%, so the schema already documents both username and fields parameters, including the default field set. The description adds only the 'by username' framing and does not add syntax or format details beyond the schema.

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 specific verb and resource: look up another Instagram Business/Creator account's public info by username. The word 'another' helps distinguish it from an own-profile lookup such as ig_get_profile, though no sibling is named explicitly.

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?

Usage is implied: use this when you need public information about a different Business/Creator account by username. The description does not explicitly say when not to use it or when to prefer alternatives like ig_get_profile or threads_lookup_profile.

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