instagram_profile

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two useful behavioral facts beyond the schema: the operation costs 1 credit and only works for public accounts. It stops short of describing auth requirements, rate limits, or error behavior.

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 tight sentences: the purpose and returned fields are front-loaded, and the cost is appended as a discrete trailing note. No filler or 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?

Despite having no output schema, the description enumerates the returned fields, and both input parameters are fully specified in the schema. For a simple read-only endpoint this is nearly complete; only caller prerequisites (public account only) are lightly touched.

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%, with both user_id and username fully documented (including that either works and that a URL is acceptable). The description adds nothing to parameter meaning, so the baseline of 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 and resource ("Get an Instagram profile") and enumerates the exact data returned: follower/following/post counts, bio, links, category, verification and HD picture. This clearly separates it from siblings like instagram_posts or instagram_comments, though it never explicitly names the distinction from instagram_user_id/instagram_username resolvers.

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 by the content described, and the phrase "any public account" hints at a constraint (private accounts presumably unsupported). However, no alternative sibling is named and no condition for choosing this over instagram_username or instagram_user_id is given.

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