create_time_activity

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it adds almost nothing beyond the word 'Create'. It does not mention required permissions, whether the entry is billable by default, how employee vs vendor attribution affects downstream behavior, or what the response contains.

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 single sentence is front-loaded and free of waste, but its brevity here reflects under-specification rather than economy. There is no structure beyond one clause, so nothing is reinforced for a tool with eleven nested fields.

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?

This is a nested-object mutation tool with a conditional required reference, no annotations, and no output schema, yet the description covers none of that. An agent would have to reverse-engineer required combinations from the schema, which is a substantial gap for a create operation.

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 reported at 0% for the single top-level 'params' object, and the description compensates with zero parameter information. Critically, the conditional requirement (employee_ref when name_of is Employee, vendor_ref when name_of is Vendor) is never surfaced in the description, leaving the most error-prone aspect of this tool undocumented at the description level.

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 states a specific verb (Create) and resource (time activity), with a clarifying gloss '(time tracking entry)' and the target system 'QuickBooks Online'. It is clearly distinguishable from update_time_activity, delete_time_activity and search_time_activities by the verb, though it never explicitly references those siblings.

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?

There is no guidance on when to use this versus alternatives, no prerequisites, and no mention of the fact that the entry must be attributed to either an employee or a vendor. The agent must infer all usage conditions from the schema alone.

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