get_unifi_manual

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

With no annotations, the description carries the full burden and does well: it discloses that the source is vector artwork with no PDF, that the tool reconstructs pages, and that it writes files to disk (a side effect an agent must know about). It omits where files land, whether an existing file is overwritten, and any auth or rate-limit 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?

Front-loaded with the action and resource, then the reason it exists, then format guidance and the exclusion. Slightly longer than needed because the format sentence duplicates the schema enum text, but no sentence is filler.

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 two-parameter tool with no output schema, the description covers what is produced (a PDF, per-page PNGs, or SVG sources written to disk) and why the textual route is impossible. Missing only operational specifics like output path and overwrite behavior.

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% with clear enum descriptions for url and format, so the baseline is 3. The description's "one combined file" vs "one image per page" framing restates the schema's pdf/png semantics rather than adding new detail such as file naming or resolution.

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 ("Download a Ubiquiti UniFi installation guide") plus the exact URL pattern it operates on. It further distinguishes itself from generic fetching and from the store/techspecs pages, so an agent can tell what this tool does and does not cover without opening the schema.

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?

Explicitly routes the agent away for adjacent intents ("For a device's specifications or price, fetch its store or techspecs.ui.com page instead") and explains which format to pick for which output need. It does not name any sibling tool as an alternative, which keeps it 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.