timezest_teams_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 of behavioral disclosure. It discloses only that the tool lists teams; it does not mention pagination, filtering, or response structure. It is not misleading, but it is minimal and leaves behavioral traits undisclosed.

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, easily parsed sentence with no filler. It is appropriately front-loaded with the core action and resource. Nothing is redundant or oversized.

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 2-parameter list operation with no output schema, the description is minimally adequate, but it does not explain the meaning of "available for scheduling" or how filter/pageSize affect results. It lacks behavioral details such as pagination and default limits, which an agent might need. The schema compensates for parameter details, so the overall context is sufficient but not rich.

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 both filter and pageSize already described in the input schema. The description adds no parameter-level detail beyond what the schema provides. This aligns with the baseline score of 3 for high schema coverage.

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 and resource: "List all teams available for scheduling." It clearly identifies a collection-returning operation and naturally differentiates from the sibling timezest_teams_get, which is a singular fetch. The phrase "available for scheduling" adds useful context about the tool's purpose.

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 use this tool versus alternatives. It does not mention timezest_teams_get or any other sibling, nor does it provide exclusions or conditions. The name implies a list operation, but the description gives no explicit usage context.

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