document_series_create

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

Explains the default currentNumber semantics (default 0 means first document gets number 1), which is valuable behavioral context. However, with no annotations provided, the description does not disclose write/safety characteristics, side effects, or permission requirements. It's decent but leaves behavioral burden unmet for a creation 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?

Three concise, front-loaded sentences with no wasted words. The uniqueness constraint, patterns, and default-number semantics are all genuinely useful. Slightly dense but efficient and relevant.

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 creation tool with 5 params and no output schema or annotations, the description covers the core purpose and the trickiest param (currentNumber). However, it omits behavioral details like return values, permission requirements, or consequences of errors (e.g., duplicates). Adequate but with meaningful gaps for a mutation tool.

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% (all 5 params have descriptions), so baseline is 3. The description adds value by explaining the currentNumber default behavior and pattern examples for prefix, but companyId and active are fully covered by the schema already. Does not exceed baseline significantly.

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?

Clear verb+resource ('Create a new document series') with an explicit uniqueness constraint (prefix unique per company and document type). Distinguishes itself from siblings by addressing series creation specifically, distinct from document_series_update, _set_default, and _delete.

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?

Provides concrete naming conventions and patterns ('FAC' for invoices, 'FAC2026' for annual series), plus the uniqueness requirement per company and type. No explicit when-not-to-use or alternative naming, but the practical context is strong and actionable.

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