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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered without the description restating it. The criteria parameter documentation goes beyond the annotation by disclosing one-page/1000-record behavior, truncation, and lack of OR support, but the one-line description itself adds no behavioral nuance. Since annotations carry the safety burden and the schema adds needed behavior details, a 3 is appropriate.

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, front-loaded sentence with no filler or repetition. It lets the detailed criteria parameter description carry complexity instead of duplicating it, making the definition appropriately sized.

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 read-only annotation and the very detailed criteria schema, the definition is complete enough for an agent to invoke it correctly: criteria behavior, page size, truncation, and filter limitations are all documented. The only meaningful gap is the absence of explicit routing guidance between this and related get/search tools.

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%, with the 'criteria' parameter extensively documented: accepted shapes, operators, field restrictions, case sensitivity, and pagination semantics. The description text adds no additional parameter meaning beyond what the schema already provides, so it sits at the baseline 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?

The description names a specific action ('Search') and resource ('time activity records') scoped to QuickBooks Online, so an agent can tell what the tool does. It does not explicitly contrast itself with get_time_activity or other search tools, though the 'search' verb implies a listing/filtering behavior.

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 prefer this over get_time_activity, when not to use it, or which tool should be chosen in alternative situations. The schema's criteria documentation implies operational usage and pagination strategy, but the description itself provides no when-to-use context.

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