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

The description adds substantial behavioral context beyond annotations: it sends nothing, drafts arrive in the normal pending batch, fit checks are skipped, contacts are still verified, already emailed or blocked sites are skipped, large sites require an email, and re-imports can requeue skipped sites. This is exactly the kind of operational detail an agent needs for a mutating import tool.

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 description is dense but front-loaded, starting with the core action and immediately adding scope and behavior. Every sentence carries operational information, including limits and side effects, with no 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 mutation tool with no output schema, the description covers the important behavior: no sends, pending-draft destination, deduplication, verification, and the 1,000-site cap. It does not describe the return value or error response, but otherwise gives an agent enough to invoke it correctly.

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 the schema already documents url, name, note, email, and workspaceId. The description reinforces what each entry represents and mentions the note reaching the draft, but adds no new syntax or constraints for workspaceId or the site fields beyond the schema.

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 verb and resource: queue sites the person has vetted for pitching. It is clearly distinct from sibling tools like add_keywords and list_imported_sites, and the title reinforces the exact scope.

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 explains when these sites are used: next runs take them first and skip the agent's own fit check, while still verifying contacts and avoiding already-emailed or blocked sites. It gives important conditions such as re-import behavior and the Forbes-class rule, but does not explicitly name alternatives like list_imported_sites.

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