threads_call

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

No annotations are provided, and the description does not disclose potential side effects (e.g., POST/DELETE can mutate data), error handling, or authentication requirements. As a generic passthrough, this is a significant gap.

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 two-sentence description is concise, front-loads the purpose, and provides essential context (base URL) without unnecessary detail.

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 provides the base URL and scope, but does not describe output format, error behavior, or authentication. Given it's a passthrough to an external API with no output schema, some gaps remain, but the core purpose is covered.

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?

Only the path parameter has an example description in the schema; query and method lack any explanation in both schema and description. The description mentions path relative to base URL but does not clarify query semantics or method usage.

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 it is a passthrough for any Threads Graph API endpoint not covered by sibling tools, with the base URL provided. This distinguishes it from the specific sibling tools.

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 explicitly says to use it for anything the tools above do not cover, and explains that paths are relative to the base URL. This gives clear guidance on when to select this tool over more specific ones.

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