Get form details

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses a key behavioral trait: the response has no ready-made embed snippet, and the caller must serve the HTML or build an embed around the form uuid. This is genuinely useful context for agent expectations.

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?

Two concise sentences front-load the purpose, then add a necessary caveat about the embed snippet. Every sentence earns its place with no filler.

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 simple read-only tool with full schema coverage, the description is nearly complete: it states what the response contains, what it lacks, and the two required parameters are in the schema. The only gap is not describing the response shape in more detail, but with no output schema the existing information is reasonably sufficient.

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%, so the baseline is 3. The description adds slight context for formUuid ('build your own embed around the form uuid'), but profileUuid remains unexplained and the schema's parameter descriptions are tautological ('Form uuid parameter'). No meaningful semantics are added.

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 and resource: 'Get a single form' and lists the key response components (URL of hosted template, tags applied to captured contacts). This clearly differentiates it from sibling tools like reach_listFormsV1, which lists forms rather than retrieving one.

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 usage context is implied: this is the tool to use when a single form's details are needed. However, it does not explicitly state when to use this versus reach_listFormsV1 or other reach tools, and it offers no exclusions or alternative guidance.

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