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

No annotations are provided, so the description carries the burden. It clearly states it is a read operation ('Read ONE Meta Instant Form') and adds a valuable behavioral detail: 'warnings name anything the form uses that Adsap cannot recreate (e.g. conditional logic)'. It also mentions the return shape matches another tool, giving the agent a sense of the response structure. It doesn't cover error conditions or auth, but for a simple read that's acceptable.

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 three sentences, front-loaded with what the tool reads and then immediately routing to the listing sibling. Every sentence earns its place: content scope, use cases, and an explicit alternative. No fluff or repetition.

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 read-only tool with no output schema, the description is complete: it states what is returned, how to obtain the form_id, and how to differentiate from listing. The mention of warnings and the shape reference to adsap_manage_instant_form provide sufficient context for correct invocation. Nothing critical is missing.

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 coverage is 100% and all three parameters are clearly described in the schema. The description adds no extra parameter details beyond what the schema provides, but it does reinforce the source of form_id ('from adsap_list_meta_assets'). This meets the baseline for complete schema coverage without adding redundancy.

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 verb ('Read'), a specific resource ('ONE Meta Instant Form'), and enumerates the content returned (questions, intro, privacy policy, etc.). It explicitly differentiates from listing via adsap_list_meta_assets and references the shape of adsap_manage_instant_form, so an agent can distinguish it without inspecting the schema.

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 gives explicit use cases: 'explain a form to the user or to prepare a duplicate' and explicitly directs listing to 'adsap_list_meta_assets (asset_type instant_forms)'. This provides clear when-to-use and when-not-to-use guidance with the alternative named.

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