qbo_time_activities_list

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

No annotations provided. The description implies a read operation (list) but does not disclose additional behavioral traits like rate limits, authentication requirements, or what happens if no results. For a list tool, the behavior is mostly obvious, but more detail could help.

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?

Single sentence of 12 words, front-loaded with the key action 'List TimeActivity records'. No unnecessary words.

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?

Description is adequate for a simple list tool with 4 optional parameters. It mentions the resource, pagination, and date filtering. No output schema exists, but the description does not need to detail return values beyond what is implied by a list 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?

Input schema covers all 4 parameters with descriptions. The description adds no additional meaning beyond what the schema already provides. With 100% schema coverage, baseline score is 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?

Description clearly states the tool lists TimeActivity records with pagination and optional TxnDate range. This distinguishes it from sibling tools like qbo_time_activities_get (single record) or qbo_time_activities_create.

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 implies usage for retrieving multiple records with filtering and pagination, but does not explicitly state when to use it versus alternatives or mention any exclusions. The context from sibling names helps but is not explicit.

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