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

readOnlyHint already covers the safety profile, and the description adds genuinely useful behavior beyond annotations: the endpoint is unpaginated and bounded to 5,000 rows/2 MiB, results are filtered by credential permissions and scheduling filters, and personal reasons are excluded. This is substantive operational context an agent cannot get from the schema.

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?

Three dense sentences, front-loaded with the route and payload contents, with limits and permission behavior following. No filler, though the includePersonal mention is wasted text on a nonexistent parameter.

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?

The description helpfully enumerates return fields, compensating for the absence of an output schema. However, with four fully undocumented parameters and no output schema, the definition leaves the agent guessing how to filter results, which is a real gap for a listing 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 0% and none of the four actual parameters (staffId, inactive, locationId, classesOnly) are explained. Worse, the description references an 'includePersonal=0' parameter that does not exist in the schema, which is misleading rather than compensating for the coverage gap.

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?

States a specific verb and resource ('Read service/reason IDs, names, duration and pricing' for GET /services), making it clear this is a bulk listing of services. It is distinguishable from the singular timetap_get_service sibling by the plural listing nature, though it never explicitly names that sibling.

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?

Usage context is implied through scoping notes ('private PERSONAL reasons are excluded', 'Results reflect the credential's permissions and scheduling filters'), but there is no explicit guidance on when to call this versus timetap_get_service or how the filters (staffId, locationId, classesOnly) should be chosen.

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