create_manual_entry

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

The annotations indicate a non-read-only, non-idempotent, non-destructive operation, but the description adds no behavioral context such as required permissions, side effects, or reversibility. It simply repeats the obvious.

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?

While brief, the description is under-specification, not conciseness. It doesn't earn its place because it duplicates the tool name.

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?

The tool is moderately complex (three entry types, an entries array with undefined structure), yet the description provides no context about how to construct entries or what the response will be. No output schema exists, so the description should fill that gap but is almost empty.

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 description adds no parameter semantics. The schema covers type (with examples), date, and reference_nr, but the essential 'entries' parameter lacks a description. With 75% schema coverage and a truncated type description, the description should compensate but doesn't.

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 is a tautology—'Create manual entry' restates the tool name without explaining what a manual entry is or how it differs from other create_* tools. Sibling tools like update_manual_entry and list_manual_entries imply a CRUD resource, but the description offers no specifics.

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 about when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or related tools such as upload_manual_entry_file_file or create_order.

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