connectif_purchases

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Direct Connectif API operations' which implies low-level API access, but does not disclose authentication requirements, mutation vs. read operations, rate limits, or effects. No behavioral traits are revealed beyond the vague 'direct' label.

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 concise with only two sentences and gets to the point quickly. However, the second sentence introduces a non-existent parameter, making it not entirely earning its place. It is compact but not well-structured given the misinformation.

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 tool has no annotations, no output schema, and only a vague description. It lacks any information about available operations, how to invoke them, return values, or error handling. The description is completely inadequate for an agent to understand and use the tool safely.

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 input schema is empty with zero parameters, so the baseline should be 4. However, the description instructs to 'Use action to select an official operation', introducing an 'action' parameter that does not exist in the schema. This is misleading and actively harms parameter understanding, warranting a score of 1.

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 identifies the resource as 'purchases' and states it performs 'Direct Connectif API operations', but the verb 'operations' is vague and doesn't specify what exact actions are available. It distinguishes from siblings by resource, but lacks clarity on what the tool actually does beyond being a generic proxy.

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?

No guidance is provided on when to use this tool versus alternatives. The only hint is that it's for purchases, but there is no explicit context, exclusions, or mention of sibling tools like connectif_contacts or connectif_products. The statement 'Use action to select an official operation' does not clarify usage scenarios.

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