meta_exchange_token

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

Discloses key behavioral detail: on success, the token is applied in-memory immediately without restart. No contradiction with annotations; adds context beyond them.

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?

Concise and front-loaded, with every sentence adding value. No fluff.

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?

Lacks explanation of the return value (e.g., the new token). However, the tool is simple and the core purpose is clear. Incomplete for an agent to fully understand expected output.

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 already covers both parameters with descriptions (100% coverage). The description adds context about platform endpoints but not significant additional meaning for the parameters themselves.

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?

Clearly states the tool exchanges a short-lived token for a long-lived token with a specific validity (~60 days). Mentions platform-specific endpoints, distinguishing it from siblings like meta_refresh_token and meta_debug_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?

Specifies the requirement of META_APP_SECRET and mentions platform-specific endpoints (Instagram vs Threads). Lacks explicit differentiation from meta_refresh_token but contextually implies its use case.

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