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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that results include SyncToken (useful for updates) and that Id IN can batch-read, which is beyond annotations. However, it doesn't disclose pagination behavior beyond what's in the schema, truncation, or rate limits.

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 sentences with no wasted words. The first states purpose and return completeness; the second gives a usage hint. It is front-loaded and efficient, though could be slightly more structured.

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 search tool with no output schema but annotations covering safety, the description is adequate but incomplete. It conveys return completeness and a batching tip, but omits pagination limits, truncation behavior, and explicit differentiation from get_time_activity, leaving gaps an agent might need.

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 the schema already documents both parameters in detail, including criteria syntax, operators, and limitations. The description adds no additional parameter meaning beyond the schema baseline of 3.

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 (search time activity records) in QuickBooks Online, which clearly distinguishes it from get_time_activity, create_time_activity, update_time_activity, and delete_time_activity. However, it doesn't explain what a 'time activity' record actually is beyond the name.

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 mentions that results are full records so no get is needed and suggests using Id IN for reading multiple known Ids, which implies when to use search vs get. But it doesn't explicitly say when to use this tool versus get_time_activity or list alternatives or exclusions.

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