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

With annotations already covering read-only/idempotent safety, the description goes further and enumerates the actual response payload (questions with id, label, type, choices, required, conditions/shown_when, approx_max_chars; plus sections, provenance with source_url, limitations, and blank/sample PDF links) and the paging model. This is exactly the behavioral context needed since there is no output schema.

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?

Front-loaded with the purpose, then the return shape, then paging, then the read-only guarantee. Dense but every sentence carries information; the field enumeration is long but justified given there is no output schema.

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?

A read tool with no output schema, yet the description fully covers the return structure, paging behavior, the opt-in heavy 'include_mapping' debug flag implications, and the safety profile. An agent has everything needed to call it correctly and interpret the result.

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, but the description adds real meaning: 'section' is tied to the sections list of a previous response and offset/limit are framed as the paging mechanism. It adds context on how parameters interact across calls rather than restating types.

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?

States a specific verb+resource ('Read a form's questions') plus the scope and the goal it serves ('before collecting answers or creating an application'). It is clearly separable from siblings like search_forms (discovery) and update_application (the writer of answers).

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?

Gives a clear usage context (call before collecting answers or creating an application) and names the downstream tool that consumes the returned ids ('the answer key for update_application'). It also explains the paging procedure (read sections list, then pass section and/or offset). No explicit when-not-to-use statement, so not a full 5.

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