superops_technicians_get

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

The description adds value by stating it returns 'detailed information', implying more than just an ID, but does not specify what fields are returned, permissions, or side effects. With no annotations, the description carries the burden but is minimal for a simple get operation.

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 with no fluff, directly conveys the purpose. 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?

Given the simplicity of the tool (one param, no output schema, no annotations), the description is adequate but could be improved by specifying what 'detailed information' includes or that it's a read-only operation.

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 description coverage is 100% (the schema describes 'technicianId' as 'The unique technician ID'). The description adds no extra meaning beyond the schema, so baseline 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 clearly states the verb 'Get' and the resource 'detailed information for a specific technician by their ID', which distinguishes it from sibling tools like 'list' (returns multiple) and other 'get' tools for different resources.

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?

It explicitly specifies when to use: when you need detailed info for a technician by ID. It doesn't explicitly mention when not to use or alternatives, but the context of sibling tools implies that for listing, use 'list'.

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