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

No annotations are provided, so the description must carry the full load. It does disclose the read semantics indirectly ('returns', GET endpoint) and the workflow role, but says nothing about how the 'view' parameter changes the response, response size, or any constraints on calling it repeatedly.

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 with the sequencing cue front-loaded and zero filler. The parenthetical REST path adds technical detail that's borderline useful but not wasteful.

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?

The description conveys what comes back (questions plus a JSON template to fill), which partly substitutes for the absent output schema. But the 'view' control over that response is undocumented, leaving a gap an agent would hit when deciding how detailed a template to request.

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 0% for the single 'view' parameter, and the description doesn't mention it at all. The enum values (lean/smallest/requestSchema/full) suggest output verbosity, but the agent is left to infer that, so the description fails to compensate for the coverage gap.

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 and resource ('returns the questions and JSON template') and ties itself to the sibling tool unifi_estimate via 'Step 1' and the name reference. An agent can tell it apart from unifi_estimate, though the description never spells out the division of labor explicitly.

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?

'Use when the person wants a price for a project' gives a clear triggering condition, and 'Step 1' implies the follow-up call to unifi_estimate. No explicit exclusion or when-not guidance, so it falls short of a 5.

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