Get account profile

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

Annotations already declare readOnlyHint and openWorldHint, but the description goes further: it names the underlying endpoint (GET /{ig-id}), discloses that hidden/omitted fields are silently absent rather than null or errored, and warns that several returned fields are untrusted free text wrapped in a content fence — a genuinely useful safety disclosure beyond the annotations.

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?

Three tight sentences: the returned-field list front-loads the payload, followed by the read-only endpoint and then the caveats. No filler and no repetition of the title.

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?

With a full input schema, an output schema, and read-only/open-world annotations already in place, the description covers the remaining gaps an agent needs — scope of the account, absent-field behavior, and the untrusted-content framing. Nothing material 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 a single optional parameter and the schema describes it fully (100% coverage), including the multi-account semantics and the IG_ACTIVE_PROFILE default. The description adds nothing about the account parameter, so the 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 (Fetch) and resource (profile of the operated Instagram professional account) and enumerates the exact returned fields, which cleanly separates it from analytics siblings like instagram_get_account_insights or instagram_get_audience_demographics.

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?

The phrase 'of the operated Instagram professional account' implies the scope, but there is no explicit when-to-use guidance and no named alternative for the adjacent questions an agent might have (e.g. follower counts over time → instagram_get_account_insights). Usage is inferable rather than stated.

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