Exchange Instagram OAuth Code

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

No annotations are provided, so the description must disclose all behavioral traits. It mentions 'save it outside the repo' but does not elaborate on side effects, failure modes, authorization requirements, or what happens if the save parameter is false. The description is minimal and lacks transparency for a mutation operation.

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 a single sentence, front-loaded with the action, and contains no unnecessary words. It efficiently conveys the tool's purpose and an optional behavior.

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?

The description covers the core operation but omits what the tool returns (e.g., the token itself) and how it integrates with other tools. For a token exchange tool, a brief mention of output or next steps would enhance completeness.

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 0%, so the description must add meaning. It identifies the 'code' parameter as the authorization code and the 'save' parameter as an option to persist the token. This adds value beyond the bare schema, though details like format or behavior of save are missing.

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 clearly states the action ('Exchange') and the resource ('Instagram authorization code for a long-lived token'), and distinguishes from sibling tools like meta_build_login_url (which builds the URL to obtain the code) and meta_refresh_token (which refreshes an existing token).

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?

While the context of exchanging a code for a token is implied, the description does not explicitly specify when to use this tool versus alternatives like meta_refresh_token or meta_build_login_url. No when-not-to-use or prerequisite conditions are provided.

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