get_private_worker

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

No annotations provided; description does not state read-only nature, authentication prerequisites, error conditions, or rate limits. Fails to disclose behavioral traits beyond the basic action.

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?

Two sentences, no fluff, front-loaded with purpose. Every sentence is necessary.

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?

Simple GET tool with one parameter and an output schema (not shown). Description adequately covers the purpose and parameter. Lacks only minor behavioral details, which are less critical given output schema.

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?

Description adds example format 'pw_...' for worker_id, which adds value beyond the schema's title. However, schema coverage is 0% and the added context is minimal.

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?

Clearly states it gets one private worker, includes the HTTP method and endpoint. Distinguishes from sibling list_private_workers which retrieves multiple.

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?

Implied usage: use when you need a specific private worker by ID. No explicit guidance on when to avoid or alternatives among siblings.

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