timezest_agents_list

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

No annotations are provided, so the description carries the full burden. It only says 'List all agents' – a read operation – but does not disclose pagination, filtering behavior, ordering, or whether the list reflects current availability. The filter parameter implies 'all' is overridden by filters, which is unaddressed.

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 with the action and resource front-loaded; no redundant words. It is as concise as possible while conveying the core purpose.

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 simple list endpoint with two optional parameters, the description plus schema is mostly adequate. However, the lack of an output schema and any behavioral notes (pagination, filtering semantics) leaves the agent without a clear picture of return shape and edge cases.

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%; both 'filter' (with TQL example) and 'pageSize' (with default/max) are documented. The description adds no parameter-level detail, so baseline 3 applies.

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 a specific verb ('List') and resource ('agents (technicians)'), with a useful qualifier 'available for scheduling'. It distinguishes from timezest_agents_get (list vs get) but does not explicitly contrast with other list tools like teams or resources.

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 phrase 'available for scheduling' gives some context for when to call it, but there is no explicit guidance on when to prefer it over timezest_agents_get or how filtering interacts with 'available'. No alternatives or exclusions are named.

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