search_time_activities

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

No annotations are supplied, so the description carries the full behavioral burden and provides almost none of it. "Search" weakly implies a read-only, non-mutating call, but there is no statement about default result limits, ordering, whether filters are ANDed together, or what a result record 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?

A single front-loaded sentence with zero filler, which is structurally sound. It is concise to the point of under-specification, though: the brevity reflects missing content rather than efficient communication.

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 tool with six filter fields, a nested object, no annotations and no output schema, one sentence is not enough. An agent cannot tell what a time activity record looks like, how dates must be formatted, or how many results come back by default, so it would have to guess before calling.

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?

Top-level schema description coverage is 0%, and the description adds nothing about parameters. However, the nested params object does carry one-line descriptions for each filter (limit, vendor_ref, customer_ref, employee_ref, txn_date_from, txn_date_to), so meaning is not entirely absent. The description still fails to compensate for gaps like date string format, ID source, and default limit.

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 gives a specific verb and resource ("Search for time activities") in QuickBooks Online, which cleanly separates it from create_time_activity, get_time_activity, update_time_activity and delete_time_activity in the sibling list. It stops short of explicitly naming or contrasting those siblings, so it lands at clear-but-undifferentiated.

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 when-to-use guidance at all: nothing says to prefer this over get_time_activity when the ID is unknown, nothing about what to do when a search returns nothing, and no mention of pagination or result caps. The agent must infer that "search" means list/filter, which is reasonable but unsupported by any stated condition.

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