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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get details' without mentioning error handling for invalid IDs, authentication requirements, or the structure of returned details. No side effects are indicated, but the lack of any behavioral context is a notable gap.

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 zero filler words. It conveys the essential action and scope immediately, and every word earns its place.

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 single-parameter get tool with no output schema and no annotations, the description is adequate but vague. It doesn't clarify what 'details' includes or how errors surface, which an agent would need for fully correct use. It is minimally acceptable but not complete.

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 coverage is 100% and the only parameter, agentId, is already described as 'Agent ID'. The description's reference to 'by ID' adds no new semantic meaning beyond what the schema already conveys, so the baseline score of 3 is appropriate.

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 clearly states a specific verb ('Get'), resource ('agent'), and scope ('specific agent by ID'). This distinguishes it from the sibling timezest_agents_list, which implies listing multiple agents rather than fetching a single one.

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 'by ID' implies that this tool should be used when a specific agent ID is known, contrasting with a list operation. However, it does not explicitly name alternatives, provide exclusions, or state when to use list vs get, leaving usage guidance implicit rather than explicit.

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

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.

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

No annotations are provided, so the description bears the burden of behavioral disclosure. 'Get details' implies a read-only, safe operation, but there is no mention of behavior for invalid IDs, missing records, or whether any side effects occur. It is not misleading, but it is minimal.

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. It conveys the resource, action, and scoping efficiently.

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 get-by-ID tool with one required parameter and no output schema, the description is largely adequate. It could mention how to obtain the ID or error behavior, but an agent can reasonably understand what to provide and what action occurs.

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 appointmentTypeId already described as 'Appointment type ID'. The description's 'by ID' adds no extra meaning beyond the schema, so the baseline 3 is appropriate.

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 uses a specific verb ('Get details') and clearly identifies the resource ('appointment type') scoped by ID, which distinguishes it from the sibling list tool. It doesn't name the alternative explicitly, but the by-ID qualifier makes the purpose unambiguous.

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 about when to use this tool versus timezest_appointment_types_list or any other sibling. It does not mention that an appointment type ID must first be obtained via the list tool, leaving usage context to inference.

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

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

With no annotations, the description carries full disclosure burden, and it only says 'List all...'. It does not reveal that results can be filtered despite the filter parameter, how pagination behaves, whether inactive types are returned, or any side-effect/read-only guarantee beyond the verb itself.

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?

One eight-word sentence, front-loaded with the verb and resource, with no redundant phrasing. It is precisely the right size for a tool this simple.

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 two-optional-parameter list tool with no output schema, the description is acceptable but thin: it relies on the name/schema for return shape and doesn't mention sibling selection or default unfiltered behavior. It is a minimally viable description rather than a complete one.

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 100% of parameters with descriptions, including TQL filter and pageSize bounds/defaults, so baseline 3 applies. The description itself adds no parameter-level meaning, but the schema is sufficient.

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 concrete action ('List') on a clear resource ('appointment types') and adds 'available for scheduling' context. It is obvious from the singular/plural sibling pair that this is the list counterpart to appointment_types_get, but it does not explicitly name a sibling or contrast its scope, so it stops short of full differentiation.

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?

No guidance on when to choose this tool over timezest_appointment_types_get or timezest_scheduling_list. The phrase 'available for scheduling' hints at one use case, but there is no explicit when/when-not statement, so an agent must infer the appropriate context.

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

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 disclosing behavior. It only says 'list all resources' without mentioning pagination, default page size, filtering via TQL, or the response structure. An agent has no idea whether results are sorted, truncated, or how to handle large result sets.

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 concise sentence with no fluff, clearly front-loading the action. It is appropriately short for a simple list operation, though it lacks some contextual details that would improve usability.

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?

With no annotations and no output schema, the description should explain the return format, pagination behavior, and usage scenarios. It does none of this. For a tool with three optional parameters and a list operation, this is severely under-specified.

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 coverage is 100%, so all three parameters (type, filter, pageSize) are already documented with descriptions and constraints. The description adds no additional meaning beyond what the schema provides, matching the 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?

The description states a specific verb (list) and resource (all resources: agents and teams) and its context (for scheduling). It clearly distinguishes from the sibling agents_list and teams_list by covering both types in a single call, so an agent can infer its scope without opening the schema.

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 does not state when to prefer this tool over the more specific agents_list or teams_list, nor does it mention optional filters or pagination. Usage context is only implied by the name and the phrase 'available for scheduling', leaving the decision to the agent.

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

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether cancellation is reversible, whether it requires special permissions, what happens to the associated request, or whether it sends notifications. The description only names the action without revealing consequences.

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 short sentence with no wasted words. It is front-loaded with the action and resource. However, it is so brief that it misses opportunities to add behavioral or usage context, so it earns a 4 rather than a 5.

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 mutation tool with no annotations and no output schema, the description is too thin. It does not explain what happens after cancellation, whether the request must be in a certain state, or how the agent can verify success. The schema covers parameters, but the behavioral and workflow context is missing.

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. The description adds no extra meaning beyond the schema, but the baseline of 3 applies because the schema does the heavy lifting. The 'reason' parameter's optionality and purpose are clear from the schema.

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 clear verb and resource ('Cancel a scheduling request'), which distinguishes it from the create/list/get siblings. However, it is terse and doesn't specify what 'cancel' means in this system (e.g., whether it cancels a pending request or an existing appointment), so it is adequate but not fully clarifying.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention that it is for canceling a previously created scheduling request, nor does it contrast with timezest_scheduling_list/get or timezest_scheduling_create_request. The context is implied by the name and description only.

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

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 says 'Create', implying a mutation, but it does not disclose side effects, prerequisites, authentication needs, or response behavior. It also fails to flag that appointmentTypeId is described as 'required' in its parameter description but is not in the top-level required array, which could mislead. The 'supports PSA ticket association' phrase is too vague to count as meaningful transparency.

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 concise sentence, front-loaded with the action. However, it is so sparse that it omits valuable guidance, making it feel under-specified rather than efficiently concise. It earns points for being short but loses for not packing more meaning into the available 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?

Given the tool's complexity (7 parameters, nested objects, no output schema, no annotations), a one-sentence description is inadequate. It doesn't explain return values, prerequisites, behavior on failure, or how it differs from list/get siblings beyond the verb. The lack of usage or behavioral context makes it incomplete for an agent to invoke correctly.

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 coverage is 100%, so the schema fully documents all parameters, earning a baseline of 3. The description adds no additional parameter-level meaning beyond what the schema provides; 'supports PSA ticket association' loosely maps to the associatedEntities parameter but does not explain it. This is exactly the baseline case where high schema coverage makes the description's contribution marginal.

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 clearly states the action ('Create') and the resource ('scheduling request'), and the phrase 'supports PSA ticket association' adds a distinguishing feature. It differentiates from sibling tools like timezest_scheduling_get and timezest_scheduling_list by naming the create operation. It loses a point because 'scheduling request' is somewhat generic and could be more explicit about what the request does (e.g., booking an appointment).

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 provides no guidance on when to use this tool versus the sibling scheduling tools (get, list, cancel). It does not mention alternatives, exclusions, or conditions that would select this tool. The only hint, 'supports PSA ticket association', is a feature description rather than usage guidance.

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

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

No annotations are provided, so the description carries the transparency burden. 'Get' signals a non-mutating lookup, but there is no mention of not-found behavior, response shape, or access requirements.

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?

A single front-loaded sentence states the operation, resource, and identifying input with no filler or duplication of schema content.

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 single-parameter getter with no output schema, the description provides the essential invocation context. 'Details' is somewhat vague, but the tool is simple enough that no critical information is missing.

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 coverage is 100%, so the requestId parameter is already documented. The description adds no meaning beyond reinforcing that the ID identifies the scheduling request.

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 uses a specific verb and resource ('Get details for a specific scheduling request') and scopes it by ID, which cleanly distinguishes it from sibling tools like timezest_scheduling_list and timezest_scheduling_cancel.

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?

'by ID' implies use when an agent already has a requestId and wants a single request's details, but the description never explicitly says when to prefer this over list/cancel or what conditions rule it out.

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

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

There are no annotations, so the description must disclose behavioral traits itself. 'List scheduling requests' only implies a non-mutating read operation and says nothing about important behaviors such as pagination being fixed at 20 records, the `status` query parameter being ignored by TimeZest, or the legacy status alias mapping. These details are buried in parameter descriptions rather than surfaced in the tool description.

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 extremely concise and front-loaded, with no wasted words. However, it is under-specified: it omits any mention of filtering, status handling, pagination, or return value, so its brevity comes at the cost of usefulness. It is a clear lead-in but not a sufficient definition on its own.

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?

With no annotations and no output schema, the description alone is not enough for an agent to confidently understand the tool's behavior and selection context. The parameter schema covers invocation details well, but the definition still lacks an explicit statement about what a scheduling request is, what the list response contains, or how this list call relates to the other scheduling 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%, so the baseline is 3. The tool description adds nothing about parameters, but the input schema already provides rich detail for `filter`, `status`, and `pageSize`, including TQL syntax, status aliases, and pagination constraints. No additional parameter meaning is needed from the description.

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 uses a specific verb ('List') with a clear resource ('scheduling requests'), so an agent can tell this is a read operation for multiple items. It is distinguished from the singular `timezest_scheduling_get` and from `timezest_scheduling_create_request` / `timezest_scheduling_cancel` by its list-oriented wording, though it does not explicitly state those contrasts.

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?

No guidance is given about when to use this tool versus alternatives such as `timezest_scheduling_get` or `timezest_scheduling_create_request`. There is no statement about using it for browsing/filtering requests or about when another scheduling tool would be more appropriate, so the agent must infer usage from the name and sibling list.

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

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly implies a read-only status operation with no parameters and no side effects. It does not explicitly state 'no side effects', but the wording is sufficient for a no-argument status tool.

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 compact sentence that front-loads the primary purpose and includes no redundant or filler content. Every word earns its place.

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 zero-parameter status tool without an output schema, the description adequately conveys what the agent will learn: connection status and available tools. It does not detail the exact format of the response, but that is a minor gap for a simple introspection tool.

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?

There are no parameters, and the schema has full coverage with an empty object. The description adds no parameter details, but none are needed. The baseline for zero-parameter tools is 4.

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 uses a specific verb ('Show') and resource ('TimeZest connection status') and adds 'available tools', making it clear this is an introspection/meta tool. It is readily distinguishable from all sibling tools, which are domain operations.

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 context for use is implied: an agent would call this to check connectivity or discover what tooling is available. However, there is no explicit guidance about when to prefer this over siblings or whether it should be called before other operations.

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

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

No annotations are provided, so the description must convey behavior. 'Get details' clearly indicates a read-only, non-destructive operation, which covers the main safety concern. However, it does not disclose error behavior for an invalid or missing team ID, permission requirements, or whether the response includes the full team object or a subset of fields.

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, compact sentence containing only essential information: the action, the resource, and the identifier. Every word contributes meaning, and there is no redundancy or filler.

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?

This is a simple one-parameter, read-only getter with no output schema. The description is sufficient for an agent to select and invoke the tool correctly, but it omits details about the expected return structure (what 'details' means) and potential error conditions. These gaps are minor given the operation's low complexity.

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?

The schema already defines teamId as a required string with the description 'Team ID', giving 100% schema coverage. The description adds no additional meaning beyond echoing 'by ID', such as where to find the ID, format expectations, or relation to the ID returned by timezest_teams_list. Per baseline for high schema coverage, this is adequate.

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 clear verb ('Get'), a specific resource ('team'), and the distinguishing scope ('by ID'). It differentiates from the sibling timezest_teams_list, which presumably fetches all teams, by targeting a single team. The wording is unambiguous and actionable.

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 'by ID' implies this tool is for fetching one team when the ID is already known, while to enumerate teams the agent would use timezest_teams_list. However, this is only implied rather than explicitly stated; there is no direct guidance on when to prefer this tool over siblings or how to obtain a team ID.

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

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

No annotations are provided, so the description carries the behavioral burden. It does disclose a meaningful behavior: deleted teams are omitted, and the returned set matches the live resource set. However, it does not address read-only behavior, pagination, or response shape, though for a simple list tool this is a partial but acceptable disclosure.

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 filler. The primary action is front-loaded, and the deleted-teams caveat is a necessary behavioral detail. Every sentence earns its place.

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 operation with two optional, fully documented parameters, the description covers the main caveat (deleted teams omitted) and the live-set consistency. No output schema exists, so return-value details are not described, but this is a minor gap for a straightforward list tool.

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 input schema fully documents both parameters, filter and pageSize. The description adds no parameter-specific semantics beyond 'list teams,' which is appropriate given the 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 opens with a specific verb and resource: 'List teams available for scheduling.' It further clarifies the scope by stating deleted teams are omitted. It does not explicitly differentiate this tool from siblings like timezest_teams_get or timezest_resources_list, though the mention of resources_list hints at the relationship.

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?

No explicit when-to-use guidance is provided. The description mentions timezest_resources_list and that teams from GET /v1/resources still return, but it never states under what conditions an agent should choose this tool over a sibling such as timezest_resources_list or timezest_teams_get.

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