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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine context beyond that: the meaning of each status ('Action required means a contract waits for your countersignature') and the auth requirement (Cotlet API key with app access). It omits pagination behavior implied by the cursor parameter, so it adds value but not rich behavioral detail.

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 front-loaded statement of scope is good, but 'Lists forms sent from projects, the same forms as Forms, All forms in Dubsado' is redundant and reads like an artifact of concatenated source text. Several short sentences earn their place (status semantics, auth), while that one does not.

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, no-required-param list tool with full schema coverage and an output schema absent, the description covers filtering, status meanings, auth needs and next-step routing, which is sufficient. Only pagination behavior is left for the agent to infer from the cursor parameter.

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% and all five parameters are documented in the schema, so the baseline is 3. The description echoes the filterable fields (type, status, project) and elaborates on status values, but adds little syntactic meaning beyond the schema; form_id is referenced only as a value to pass elsewhere, not a parameter here.

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 gives a clear verb+resource ('Lists forms') and scopes it ('across projects, or in one project'), so an agent knows what it returns. However the clarifying phrase 'the same forms as Forms, All forms in Dubsado' is awkward and does not cleanly distinguish this tool from the sibling list_form_templates or send_form.

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 states the filter dimensions ('Filter by type, status or project') and routes the agent onward with 'Pass form_id to get_form_responses', naming a concrete sibling and the condition that uses it. It stops short of explicit when-not-to-use or a direct contrast with list_form_templates.

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