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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the underlying endpoint (GET /reports/{identifier}/fields.json) and the shape equivalence to wufoo_get_form_fields, but says nothing about error behavior for unknown reports or response size.

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 tight sentence plus an endpoint note, front-loaded with what is returned. Nothing is wasted, though the shape reference leans on the reader knowing the sibling tool.

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 lookup with 100% schema coverage and a readOnly annotation, the description is adequate; the 'same shape as wufoo_get_form_fields' clause substitutes for an output schema. Only error/edge-case behavior is unaddressed.

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%, so both parameters (report identifier and the system metadata flag) are fully documented in the schema. The description adds no parameter-level detail beyond that, making 3 the correct baseline.

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: retrieving the field structure of the form a report is built on. The parenthetical relating it to wufoo_get_form_fields helps disambiguate it from the sibling, though it stops short of a full explicit contrast.

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?

No when-to-use or when-not guidance is given. The description notes the output matches wufoo_get_form_fields, but never says when an agent should call this instead of that sibling (e.g., when only the report identifier is known).

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