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

Annotations only say this is a non-read-only, non-destructive, non-idempotent, closed-world write; the description adds the substantive behavior: nothing is published, the human must sign in via reviewUrl and submit, MakerRadar then reviews it, and an already-listed site short-circuits to its existing page. It also resolves the auth question with "No sign-in needed," which an agent would otherwise have to guess.

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?

The core action and its inputs come first, followed by the return value and the publish gate, then edge cases. Every clause carries information an agent needs; there is no filler or repetition of the title.

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 four-parameter draft-creation tool with full schema coverage and an output schema, the description covers the action, the inputs, the return value (reviewUrl), the human-approval gate, and the already-listed fallback. Nothing needed to call it correctly or set expectations with the user is missing.

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% and each parameter already carries type and length constraints (2–60, 4–90, 40–4000 characters). The description only restates that url is required and the rest optional, adding no format or content guidance beyond the schema, 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?

States a specific verb and resource ("Draft a listing on MakerRadar") and scopes it to the person being helped, which cleanly separates it from submit_listing and update_listing. It also makes the draft-only nature explicit ("nothing is published until they do"), so an agent can tell it apart from the publishing siblings without reading either 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?

Gives a clear context for use ("for the person you're helping") and an edge case ("If the site is already listed, returns its page instead"), which tells the agent what to expect on a repeat call. It stops short of explicitly naming submit_listing as the follow-up tool, but the reviewUrl handoff makes the next step obvious.

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