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

readOnlyHint=true already covers the safety profile, and the description adds the raw endpoint (GET /reports/{identifier}/fields.json) plus the fact that output mirrors wufoo_get_form_fields. That shape hint is useful, but there is no disclosure of auth needs, pagination, or error behavior.

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, resource stated first, sibling cross-reference and endpoint afterward. No filler; every clause carries information.

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 annotations covering read-only safety and the description pointing at wufoo_get_form_fields for output shape, an agent has enough to call it correctly. No output schema exists, and the description partly compensates via the shape reference, though it stops short of describing the actual fields returned.

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 'report' (hash or URL title) and 'system' (system metadata toggle) are fully documented in the schema. The description adds only the endpoint path and does not enrich either parameter beyond that, so the 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 states a specific resource (the field structure of the form underlying a report) and explicitly anchors it against the sibling wufoo_get_form_fields by noting the identical shape, so an agent can separate 'report's base-form fields' from 'form fields directly'. The retrieval verb is implied rather than stated, which keeps it just short of a clean 5.

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 names a comparable sibling to clarify return shape but gives no when-to-use/when-not guidance and no selection criteria between wufoo_get_report_fields, wufoo_get_form_fields, wufoo_get_report, or wufoo_list_report_widgets. The agent must infer the usage context.

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