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

Annotations only flag a non-idempotent open-world write; the description goes far beyond that by disclosing the full human workflow (e-mail confirmation within 48 h, manual team review, nothing auto-published), the quota limits (3/day per author e-mail, 5/day per IP), 30-day duplicate refusal, and 7-day expiry of unconfirmed submissions.

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 English block is dense but front-loaded and every sentence carries operational weight (workflow, requirements, limits, expiry, terms link). The appended French paragraph duplicates the same content, which is defensible for a bilingual store but adds length.

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 17-parameter mutation tool with no output schema, the definition covers what an agent needs: consent precondition, required content constraints, quotas, failure/expiry semantics, a terms URL, and a pointer to submission_status for result tracking.

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 only 35% across 17 parameters, and the description compensates for the highest-risk ones: summary must be plain text, ≥200 characters, no HTML, at most 2 URLs; manuscript/cover must be public https links to pdf/epub/docx/audio and jpg/png/webp; rights_confirmed=true; author e-mail must be real. Several fields (price, currency, agent_name, notes, subtitle, isbn, category) remain undocumented in both places.

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?

Starts with a specific verb+resource ('Submit a book on behalf of its author') and scopes it to two named storefronts with concrete context (25% commission, paper/PDF/audio). It is immediately distinguishable from siblings like get_book, search_books or submission_status.

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 hard precondition ('Only submit with the author's explicit consent, using their real e-mail') and routes tracking to the sibling 'submission_status'. It stops short of an explicit when-not-to-use-this-instead rule, but the preconditions and limit/duplicate rules define the usage envelope well.

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