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

No annotations are provided, so the description carries the full burden. It discloses that the tool requires signed-in users (auth context), that it returns role and ownership info, and that only owned workspaces are administrable. It doesn't describe the exact return format, but for a list operation with no parameters, this is adequate. The description adds meaningful behavioral context beyond the schema.

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 three sentences, each earning its place: what it lists, what ownership implies, and who can call it. It is front-loaded with the core purpose and adds necessary constraints without fluff.

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 zero-parameter list tool with no output schema, the description is quite complete. It covers the resource, the result fields (role, ownership), the administrative implication, and the auth restriction. The only minor gap is the exact response structure, but that's not essential for a simple list 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?

The tool has zero parameters, so the schema provides no parameter semantics. The description compensates by explaining what the tool returns (workspaces, role, ownership) and the auth requirement. With 0 params, baseline is 4, and the description meets that by adding context about the result set.

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 lists Higgs Hub workspaces the user belongs to, including role and ownership status. It distinguishes itself from sibling tools like list_workspace_members and list_authorized_mailboxes by specifying the resource (workspaces) and the scope (workspaces you belong to).

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?

The description explicitly states when to use this tool: to list workspaces the user belongs to, and notes that only owned workspaces can be administered. It also provides an exclusion: API keys can't call this, only signed-in users. This gives clear guidance on when to use it and its limitations.

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