aiworkers_whoami

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

With no annotations, the description fully conveys that this tool is a read-only introspection call, disclosing both normal and edge-case behavior (no key returns login URL). No contradictions.

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?

Three sentences, each purposeful and front-loaded. First sentence states core purpose, second gives usage directive, third covers edge case. No redundant or extraneous text.

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 zero parameters and an output schema present, the description covers the essentials: purpose, usage order, and conditional outcome. It sufficiently differentiates from sibling tools without being overly verbose.

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?

No parameters exist, so baseline is 4. The description adds meaning by explaining what the output covers (groups, modules, endpoint map) and the conditional login URL behavior, going beyond the trivial empty schema.

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 shows what the API key can see, listing specific outputs (groups, modules, endpoint map). It distinguishes itself from siblings like aiworkers_login_link and other workers_* tools by focusing on identity/introspection.

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?

Explicitly instructs 'Call this first,' providing clear usage priority. It also describes conditional behavior when no key is present (returns login URL), helping the agent decide when to use this tool before others.

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