create_from_proforma

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

The annotations already indicate readOnlyHint=false (mutation) and destructiveHint=false (non-destructive). The description adds no new behavioral information beyond the fact that it creates an invoice. It does not mention side effects on the proforma or any required permissions.

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 a single sentence that efficiently conveys the essential purpose. There is no unnecessary information or repetition.

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 simple tool with one well-documented parameter and basic annotations, the description is minimally adequate. However, it lacks usage guidelines and additional behavioral context that could help an agent decide when to invoke it.

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?

The input schema has 100% coverage, describing document_id as 'A proforma dokumentum ID-ja'. The description does not add further meaning to the parameter beyond the schema and the tool name.

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 clearly states the tool's function: creating an invoice from a proforma. The verb 'készítése' (create) and the specific resource 'díjbekérőből (proforma) számla' (invoice from proforma) make the purpose unambiguous. It distinguishes itself from sibling tools like create_from_draft and copy_document.

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?

The description implies usage context (given a proforma ID, create an invoice) but does not explicitly state when to use this tool versus alternatives like create_document or create_from_draft. No guidance on when not to use it is provided.

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