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

With no annotations provided, the description carries the behavioral transparency burden. It communicates that the operation is a read, describes the returned shape as matching adsap_manage_instant_form, and discloses the warnings field for non-recreatable elements like conditional logic. This covers the most important behavioral aspects, though it does not discuss permissions or side effects explicitly.

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 and front-loaded: the main purpose and full field inventory come first, followed by usage context and the sibling alternative. Every sentence earns its place, and the sibling disambiguation is integrated without clutter.

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 output schema, but the description compensates by enumerating the returned fields, the structural correspondence to manage_instant_form, and the warning field's purpose. Combined with fully described parameters, an agent has everything needed to call and interpret the result.

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 description coverage is 100%, so the schema already documents all three parameters thoroughly. The description itself adds little parameter-level meaning beyond reuse context, which matches the baseline for fully covered schemas.

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 opens with a specific verb and resource: 'Read ONE Meta Instant Form in full', followed by a concrete list of what is included (questions, intro, privacy policy, thank-you screen, tracking parameters, status, lead count). This clearly distinguishes the tool from sibling getters and from listing 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?

The description explicitly states when to use the tool: to explain a form to the user or to prepare a duplicate. It also directs the agent to use adsap_list_meta_assets for listing forms, which prevents ambiguity between get and list operations.

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