search_time_activities

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

No annotations are present, and the description does not disclose behavioral traits such as whether the search is read-only, any permission requirements, rate limits, or pagination behavior. The agent is left to infer that it is a read operation.

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 a single sentence, which is concise but lacks structure. It provides minimal information, fitting into the 'efficient' category, but does not organize details like usage context or parameter hints.

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?

Given the complexity (6 sub-parameters, nested object) and no output schema, the description is insufficient. It does not mention pagination, default limits, or how results are returned, leaving significant gaps for an agent to use effectively.

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 meaning beyond the input schema. With schema description coverage at 50% (only half of top-level parameters have descriptions), the description could compensate but does not. The schema itself describes sub-parameters, but the overall params object lacks description.

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 'Search for time activities in QuickBooks Online,' which clearly identifies the action (search) and resource (time activities). It distinguishes from sibling tools like get_time_activity by implying a list/query operation.

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 on when to use this tool vs alternatives such as get_time_activity (for single item) or other search tools. The description lacks context on suitable use cases or prerequisites.

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