meta_call

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

The description discloses that the Page token is used by default and that the 'as' parameter can switch to the Instagram token, which is useful context. It does not warn about the potential side effects of using POST or DELETE methods, nor does it mention response formats or error handling, which is a gap for a generic endpoint caller.

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 compact, two sentences, with the core purpose front-loaded and the caveat about the lack of a complete catalogue following logically. It avoids redundancy and uses precise language, making it easy to parse quickly.

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?

For a generic tool with no output schema, it covers the essential how (path relative, token default) and when (catch-all for uncovered endpoints). It omits important contextual cautions regarding destructive methods (POST/DELETE) and the expected shape of the query parameter, which an agent invoking a raw endpoint would benefit from knowing.

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 coverage is 50% (path and as have descriptions; query and method do not). The description adds meaning by clarifying that paths are relative to the Graph host and version, and by touching on token selection, but it does not elaborate on the 'query' object structure or the implications of the method parameter, leaving some parameter behavior under-explained.

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 tool calls any Graph API endpoint directly, with the Page token by default, positioning it as the generic fallback. It distinguishes itself from the specific sibling tools by noting it is the way to 'reach the rest' of the API, making its purpose unmistakable.

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?

It implicitly indicates usage when no dedicated tool is available by stating 'this is how you reach the rest of it', given the siblings cover common endpoints. However, it does not explicitly say 'prefer specific tools when available' or provide examples of when to choose this over a sibling, leaving some ambiguity.

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