get_psw_schedule

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It clearly indicates a read operation through 'Get' and 'Shows', and it describes the content of the response (clients, times, locations). However, it does not disclose potential pitfalls such as permission requirements, pagination limits, or the behavior when no visits exist or when the date range is invalid.

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 two sentences long, with the first sentence stating the core function and the second adding relevant output details. It is front-loaded and contains no 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?

Given the tool's simplicity, no output schema, and complete parameter documentation in the schema, the description adequately explains the tool's purpose and expected output. It covers the key aspects: the scope (specific PSW, date range) and the content (clients, times, locations). It is sufficient for an agent to decide when to use it and what to expect.

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?

Since all three parameters have descriptions in the input schema, the schema coverage is 100%. The description adds no new semantic detail beyond what the schema already provides; it merely restates the date-range concept and 'specific PSW' without elaborating on the parameter meanings.

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 the explicit verb 'Get' and specifies the resource as 'full visit schedule for a specific PSW within a date range'. It also clarifies the output ('assigned clients, times, and locations'), which distinguishes it from sibling tools like get_psw (returns PSW profile) or get_visits (likely general visits).

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 provide explicit guidance on when to use this tool versus alternatives, nor does it name any sibling tools or exclusions. The context is implied by the phrase 'for a specific PSW', but no direct comparison or alternative is given.

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