get_user_profile

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

No annotations are provided, so the description carries the full burden. 'Fetch' implies a read-only operation, and the listed fields give a basic sense of the return data. But it does not disclose permission requirements, rate limits, failure behavior, or privacy constraints.

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 one concise sentence, front-loading the action and resource. The parenthetical field list is efficient. It is appropriately sized for a simple lookup tool, though it could be slightly more structured.

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?

Given a simple single-parameter read tool with no output schema, the description usefully names key returned fields. It still leaves gaps around return structure, error cases, and differentiation from similar profile-fetching siblings.

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 user_id already documented as the Instagram Scoped User ID (IGSID). The description repeats that the lookup uses IGSID but adds no extra syntax, format, or validation guidance 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: fetching Instagram user profile details by IGSID. It also names the returned fields, which clarifies the scope. However, it does not explicitly distinguish itself from close siblings such as get_instagram_profile or check_user_follows_account.

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?

There is no guidance on when to use this tool versus alternatives like get_instagram_profile or check_user_follows_account. The only implied usage is fetching a profile by IGSID, with no exclusions or prerequisite context.

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