freshbooks_create_time_entry

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

With no annotations, the description carries the burden and does well by disclosing the dry-run preview and no network call without confirm. It also highlights the SECONDS unit for duration. It does not cover other behavioral aspects like permissions or result format, but the most critical behavior is disclosed.

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 two sentences, front-loads the main purpose, and packs the key execution detail (confirm) and unit (seconds) without any waste. Every word earns its place.

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 description covers the essential behavior (dry-run vs. execute) but omits any guidance on the many optional parameters (client, project, service, billable, note). Given the tool's 8 parameters and lack of output schema, more context would help, but the core flow is understandable.

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 only 38%, and the description only amplifies that duration is in seconds and confirm is required for execution. It does not add meaning for the other five undocumented parameters (note, billable, client_id, project_id, service_id), so it fails to compensate for the low schema coverage.

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 with a specific verb ('Log') and resource ('a time entry'). This distinguishes it from siblings like freshbooks_list_time_entries, making the purpose immediately clear.

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 provides explicit usage context by explaining the confirm requirement and dry-run behavior. However, it does not mention when to use this tool versus other create tools or list time entries, so it lacks explicit alternatives or exclusions.

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