Get form

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds that only public-facing data is returned, which is genuinely useful scope context, but it says nothing about auth requirements, error behavior on unknown slugs, or whether the enum-typed formType must match the slug's actual type.

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?

A single front-loaded sentence with no filler; every item listed maps to actual return content. It is a fragment lacking a subject/verb, but that costs almost nothing in clarity.

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?

With no output schema, the enumeration of returned fields (title, dates, tiers, custom fields, state, URL) fills the main informational gap for a 3-parameter read tool whose annotations cover safety. Only the formType/slug relationship and failure modes remain unstated.

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%, including the orgSlug fallback to HELLOASSO_ORG_SLUG and the formType enum, so the schema does the heavy lifting. The description adds no parameter meaning beyond what structured fields already provide; baseline 3 applies.

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 names the specific resource and scope ('Public details of one form') and lists the concrete content returned (title, dates, tiers/prices, custom fields, state, URL), so an agent can distinguish it from list_forms or get_form_stats. The phrasing is a noun fragment rather than an explicit verb, but the intent is unambiguous.

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?

'one form' implies use when you already have a single form in hand, versus the sibling list_forms, but no explicit when-to-use or when-not-to-use guidance is given. Nothing tells the agent why it would pick this over get_form_stats or how the two relate.

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