baasix_get_user_tenants

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

The verb 'Get' implies a read-only operation, and 'for the current user' signals user-scoped, authentication-dependent behavior. With no annotations present, the description carries the burden, but it does not disclose potential behaviors like returning an empty list, requiring an active session, or error cases if no tenant is available.

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 entire description is one short, front-loaded sentence with no filler, redundant phrasing, or unnecessary detail. Every word contributes to conveying the tool's purpose.

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 parameterless read-only getter, the description is nearly complete: it identifies the resource and the user scope. Still, because there is no output schema, a slightly more explicit statement of the return value, such as 'returns a list of tenant objects available to the current user,' would remove the only remaining ambiguity.

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 and the input schema fully documents this with 100% coverage, so there is nothing for the description to add. The baseline of 4 for a zero-parameter tool applies here because parameter semantics are trivially satisfied.

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 uses a specific verb ('Get') plus a clear resource ('available tenants') and a scope qualifier ('for the current user'), so an agent knows exactly what the tool returns. It is also distinguishable from sibling tools like baasix_switch_tenant and baasix_get_current_user, which involve tenant switching or user profile retrieval rather than listing tenants.

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 phrase 'for the current user' implies this tool should be used to discover which tenants the authenticated user can access, and it is naturally used before a tool like baasix_switch_tenant. However, it does not explicitly state when to prefer it over alternatives, nor does it mention prerequisites such as being logged in.

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