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

With no annotations, the description carries the full burden and does reasonably well: it discloses the credit cost ('Costs 1 credit(s)') and the auth requirement ('Requires Authorization: Bearer <api_key>'), plus the fact that only public profile identity is returned. It still omits behavior for private, suspended, or nonexistent accounts and any error/rate-limit semantics, which keeps it short of 5.

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?

Front-loaded with the core action and payload, then boilerplate (Platform/Resource, cost, auth) that is genuinely useful rather than filler. Minor blemish: a stray double period in 'metadata..' and the templated 'Platform=instagram resource=user' is low-value relative to the rest.

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?

No output schema exists, so the description correctly enumerates the return fields, and with no annotations it supplies the cost and auth context an agent needs before calling. It is close to complete for a single-parameter lookup; only failure-mode behavior for inaccessible accounts 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?

There is one parameter with 100% schema description coverage, and the schema already explains 'Instagram username without @.' The description only restates 'for an Instagram username' and adds no format, casing, or URL-vs-handle guidance beyond the schema, 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 ('Fetch') and resource ('public profile identity for an Instagram username'), then names the returned fields (username, display name, verification status, profile picture metadata), which is concrete enough for an agent to know what it gets. It does not, however, distinguish itself from close siblings such as instagram_detailed, which presumably also returns profile data — a one-clause differentiation would have made this a 5.

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 purpose: call this when you need identity/profile information for a single Instagram username. There is no explicit when-to-use, when-not-to-use, or comparison against the overlapping siblings (instagram_detailed, instagram_followers, tiktok_user, threads_user), so the agent must infer routing.

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