fiken_create_credit_note_from_draft

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

Annotations indicate readOnlyHint false, confirming a write operation. The description adds no behavioral details beyond this, such as the fate of the draft after finalization, permission requirements, or side effects.

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, which is concise but at the expense of omitting crucial details about parameters and usage context. It could be expanded while remaining efficient.

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?

With no output schema and a single parameter, the description is too sparse. It does not mention prerequisites, return values, or error cases, which are necessary for correct invocation.

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 schema has 0% description coverage, and the description does not mention the 'draftId' parameter. Since the parameter name is generic, the description should explain its role (e.g., the ID of the draft to finalize).

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 that the tool finalizes a draft into a credit note, specifying the verb 'creates' and the resource 'credit note' with the source 'from a draft'. This distinguishes it from direct credit note creation tools like fiken_create_full_credit_note, but lacks additional context about what a draft is.

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?

No guidance is provided on when to use this tool versus alternatives. Given siblings like fiken_create_full_credit_note and fiken_create_partial_credit_note, the description should indicate that this tool is only for finalizing existing drafts, not for creating credit notes from scratch.

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