fiken_create_credit_note_draft

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

The description only states it creates, consistent with annotations (readOnlyHint false), but provides no additional behavioral context such as side effects, permissions, or what happens to existing data.

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 with 5 words, which is too terse; it lacks any structure beyond the minimal statement and does not earn its place by providing unique value.

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?

Given the tool's complexity (18 parameters, 3 required) and no output schema, the description is extremely incomplete; it does not explain what a credit note draft is, how it relates to invoices, or any usage context.

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?

With only 11% schema description coverage, the description does not explain any of the 18 parameters; it merely restates the tool purpose, failing to compensate for the lack of schema descriptions.

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 'Creates a new credit note draft' clearly states the action and resource, but does not distinguish from sibling draft creation tools like 'fiken_create_invoice_draft' or 'fiken_create_offer_draft'.

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 on when to use this tool versus alternatives; it does not mention any prerequisites or exclusions despite many related sibling tools.

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