Find workspaces for an email

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds important behaviors beyond the schema: 'Hits the CENTRAL host... not the per-tenant API,' 'Always 200, even for unknown emails (anti-enumeration),' and 'Free; doesn't consume credits.' These details are not inferable from the schema alone.

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?

The description is four sentences long, front-loaded with the core action and then providing use case and technical details. Every sentence adds value without redundancy or filler.

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 lookup tool with 2 params and no output schema, the description covers purpose, usage, host routing, anti-enumeration behavior, and cost. It does not describe the return format or authentication requirements, but these are arguably not essential given the tool's simplicity.

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 description coverage is 100%, so the baseline is 3. The description mentions the email lookup context and central host behavior, but it does not add specific param-level semantics beyond what the schema already provides for 'email' and 'central_url'.

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's function: 'List the Neural Draft workspaces (tenants) an email is registered against.' It uses a specific verb ('List') and resource ('workspaces'), and the context of 'an email' distinguishes it from other tools like get_gallery or list_pages.

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 provides a concrete use case: 'Useful for multi-workspace login troubleshooting — the user knows the email but forgot which workspace.' It also explains that it 'Hits the CENTRAL host... not the per-tenant API,' which clarifies when this tool is appropriate, though it does not explicitly name alternatives or exclusions.

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