cigchat_get_integration_meta_conversions_api

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds the auth requirement ('Requires the Manage Team scope'), which is useful, but it does not explain response shape, idempotency, or error behavior. The GET verb and 'Get' wording imply a safe read, but that is not explicitly stated.

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 that packs the purpose, endpoint, and auth requirement without unnecessary words. It is immediately scannable and every element contributes to correct invocation.

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 zero-parameter GET tool, the description is mostly complete: it names the resource, includes the HTTP path, and gives the required scope. It could mention what the config contains or that it returns the integration settings, but the absence of an output schema does not seriously impair selection or invocation here.

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?

The tool has zero parameters, so there are no parameter semantics to explain. The schema is empty and the description does not need to compensate for undocumented inputs. The baseline of 4 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?

The description clearly states a specific verb-resource pair: 'Get the config of Meta Conversions Api integration'. It is easily distinguished from sibling tools like get_integration_shopify, set_integration_meta_conversions_api, and clear_integration_meta_conversions_api.

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 description provides a clear prerequisite: 'Requires the Manage Team scope on the token.' It does not explicitly discuss when to use this versus set/clear alternatives, but the verb 'Get' and the presence of sibling set/clear tools imply read-only usage.

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