get_lead_form

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

No annotations are provided, so the description carries the behavioral disclosure burden. It communicates the read-only nature through 'Get' and adds the revision-selection behavior, but it does not mention permissions, default revision behavior, response shape, or any side effects.

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 short sentences with no filler. The core action and the optional revision variant are front-loaded and easy to scan.

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 GET-style tool the description is mostly adequate, but it omits ad_account_id context and does not explain what the response contains or whether the latest revision is returned when rev_id is absent. Without annotations or an output schema, these gaps reduce completeness.

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 67%: lead_form_id and rev_id are documented in the schema, and the description reinforces the ID and revision semantics. However, ad_account_id remains undocumented in both schema and description, so the agent gets no help understanding its purpose.

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 clearly states a single-resource fetch ('Get a Lead Form by ID') with an optional revision. It distinguishes itself from list_lead_forms through ID-scoping, though it does not explicitly name that sibling.

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?

Usage is implied: use this tool when you have a lead_form_id rather than wanting to list lead forms. There is no explicit guidance about when to use list_lead_forms or whether ad_account_id is required for certain contexts.

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