whoami

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

Discloses it returns specific workspace fields and verifies the key. No annotations exist, but description implies no side effects (read-only). Could mention idempotency or rate limits but sufficient for a simple check.

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 concise sentences plus a pairing suggestion. Front-loaded with purpose and return, no wasted words.

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 simple verification tool with one optional parameter and no output schema, the description covers what to expect and when to use it. Pairing suggestion adds context. Slight gap: no mention of response format beyond fields.

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?

With 100% schema coverage for the only parameter (apiKey), description adds no additional parameter details. Baseline 3 is appropriate as schema already describes the parameter's purpose and default.

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?

Description clearly states the tool verifies the API key and returns workspace details (name, plan, email quota, owner). It differentiates from siblings like get_workspace by emphasizing authentication check.

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 advises 'Call this first to confirm the key works before sending' and suggests pairing with list_domains. Provides clear when-to-use and pairing guidance.

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