pws_get_worker

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is known. The description adds a useful list of returned categories (contracts, storylines, history) but doesn't clarify details like the time range for 'recent history' or how relationships are represented. No contradiction.

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, front-loaded with the action, no filler. 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 read-only profile fetch with one obvious parameter and no output schema, the description lists the major content areas. It omits details like the shape of 'recent history' or whether 'active contracts' includes all statuses, but overall it's an adequate standalone description given the annotations.

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 has a single required workerId with no description and 0% schema coverage. The description never mentions the parameter, leaving the agent to infer that workerId identifies the worker. This fails to compensate for the lack of schema documentation, though the parameter name is self-explanatory.

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 specific verb 'Get' with 'worker profile' as the resource, and enumerates the contents ('all attributes, active contracts, relationships, chemistry, storylines, and recent history'). It differentiates from the targeted sibling pws_get_worker_contracts by framing itself as 'comprehensive', though it doesn't explicitly name alternatives.

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 guidance on when to use this vs. alternatives like pws_get_worker_contracts or pws_get_storylines. The phrase 'comprehensive worker profile' implies it's the general-purpose fetch, but there is no clear when-not or alternative mention.

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