list_psws

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

With no annotations, the description carries full transparency burden. It discloses that the tool returns home addresses and status, which is useful. However, it says 'List all PSWs' while the schema default is 'active', potentially misleading about the default behavior. It also does not mention privacy/sensitivity of address data or pagination, though those are less critical for a simple list.

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 with no wasted words. It front-loads the main action and outcome and immediately gives practical usage context. 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 tool with a well-documented single parameter and no output schema, the description adequately covers what the tool returns and why to use it. It loses one point for not clarifying the active-by-default filter, but overall it is sufficient.

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% for the single 'status' parameter, including an enum and default value, so the schema already fully explains parameter semantics. The description adds no new parameter details, 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 clearly states the tool lists all Personal Support Workers (PSWs/employees) with their home addresses and status, using the specific verb 'list' plus the resource. It naturally distinguishes from sibling tools like get_psw (single PSW) and list_clients (different resource type).

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 includes 'Use this to understand who is on the team and where they live,' giving clear context for when to use it. It does not explicitly name alternatives or exclusions, but the purpose is straightforward enough that this is acceptable.

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