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

Annotations already declare destructive/openWorld/non-idempotent, so the safety profile is covered. The description adds real behavior beyond that: list responses carry count/total/nextPage with nextPage feeding back as args, and writes are dry-run by default. Error handling and the fact that commands vary per site are not addressed.

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?

Three short sentences, zero filler, front-loaded with the core action and then the two facts an agent must know (pagination shape, dry-run default). 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 no output schema, the description does the work of describing the return envelope (count/total/nextPage) and the write-mode behavior. For a generic dispatcher over an open world of sites, it is nearly complete; only error/failure behavior and site-selection prerequisites are unstated.

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. The description adds meaning the schema does not: args is documented as the command's own parameter bag to be looked up via clify_help, and nextPage is explained as the args for the following page, establishing the pagination loop across calls.

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: call one command of a clify site and receive JSON. It names the sibling clify_help as the place to discover commands, distinguishing itself from the discovery tool. It does not distinguish itself from the per-site convenience siblings (crates__get-crate, pypi__get-package), which overlap functionally.

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?

Implies usage via the clify_help pointer and explains the write path (preview unless confirm:true), which tells the agent how to invoke safely. However, it never says when to prefer clify_run over the dedicated per-site tools listed as siblings, nor does it state prerequisites for picking a site name.

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