get_psw

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

No annotations are provided, so the description must carry the full burden. It clearly states this is a read operation ('Get') but does not disclose the return structure, error behavior, or any data scope. The phrase 'detailed information' is vague and adds little beyond the tool name and 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?

The description is a single sentence with no unnecessary words. It is front-loaded with the action and resource, scoring high on conciseness, though it may be terse.

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 tool has only one parameter and no output schema, so the description is the sole indicator of what 'detailed information' means. It does not specify the fields returned or differentiate from schedule/utilization getters, making it incomplete for an AI to predict the tool's full behavior.

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 input schema fully describes the only parameter employee_id (with description 'The AlayaCare employee ID'), giving 100% coverage. The description's 'by their ID' adds no additional meaning, so a baseline 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 uses a specific verb ('Get') and identifies the resource as 'detailed information about a single PSW / employee by their ID.' It distinguishes from sibling tools like list_psws by emphasizing 'single' and 'by their ID,' clearly indicating an individual lookup.

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 implies usage when a specific employee ID is known, but it does not explicitly contrast with alternatives such as list_psws, get_psw_schedule, or get_psw_utilization. The context is clear but no exclusions or alternative guidance are provided, leaving it at an implied level.

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