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

Annotations provide only destructiveHint=true, so the description carries the bulk of the behavioral burden. It says nothing about what the write does beyond creating a record — no note on time_log overlap rejection, no auth/permission requirements, no return value (e.g., the new task id), and no explanation of why the operation is flagged destructive.

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?

Two short sentences with zero filler and the core action front-loaded; the endpoint reference is a compact trailing detail. It is efficient, though the same brevity is also what leaves behavioral gaps.

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 mutation tool with only destructiveHint=true and no output schema, the description is too thin: it does not say what a successful call returns, whether a client_id/project_id is needed, or how logged time interacts with the task. The schema covers inputs, but the behavioral/return context an agent needs is absent.

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%, so all six parameters are fully documented in the schema (rate defaults, hashed ids, Unix timestamp semantics, overlap rule). The description adds no parameter meaning beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb and resource ('Create a task'), plus scope ('optionally with logged time entries, for a client or project') and the underlying endpoint. It is clear enough to distinguish from sibling creators like invoiceninja_create_expense or invoiceninja_create_project, though it never names those siblings explicitly.

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 when-to-use guidance, no mention of alternatives (e.g., invoiceninja_list_tasks for reading existing tasks), and no prerequisites such as needing a client_id or project_id. Only the implied 'this is how you create things' usage is present.

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