verify_form_attachment

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 only states the purpose ('Verify that attribution was copied into form fields') but says nothing about return values, error behavior, side effects, prerequisites, or what happens on success/failure. This is a significant gap for a verification tool.

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 extremely concise (one sentence), which is superficially efficient, but it under-specifies the tool. The brevity is not 'appropriate' because it omits essential details; it resembles an under-specification rather than effective conciseness.

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 nested object parameters, no output schema, and no annotations. The description is completely inadequate for an agent to understand how to call it correctly, what inputs are expected, or what the tool returns. It lacks even basic context about the verification process.

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 schema has 0% description coverage for its three parameters (fields, attribution, requiredKeys), and the description does not mention any of them. There is no explanation of what each parameter represents, their format, or their role in verification, leaving the agent unable to construct valid inputs.

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 states a specific action (verify) and a specific target (attribution copied into form fields), which gives some clarity about the tool's function. However, it does not differentiate from sibling verify_* tools like verify_capture or verify_crm_attachment; the reference to 'form fields' provides partial distinction but leaves ambiguity about what 'attribution' encompasses.

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?

There is no guidance on when to use this tool versus the many sibling tools (e.g., verify_capture, verify_conversion_delivery). No conditions, alternatives, or exclusions are provided, leaving the agent to infer the appropriate context without support.

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