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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered structurally. The description adds useful context (which fields come back, that it hits the control-plane tenants table) but says nothing about auth requirements, sensitivity of payment-provider data, or behavior when the user has multiple tenants. Adequate but not rich.

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 compact sentences with the returned-field list front-loaded and no filler. The trailing 'PostgREST: GET /tenants' is implementation detail of marginal value to an agent but costs little.

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?

With no output schema, the description compensates by naming the returned fields, and readOnlyHint covers safety. Only minor gaps remain (multi-tenant return shape, pagination via limit), which are not critical for a simple read.

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?

Schema coverage is 100% and the single 'limit' parameter is fully described in the schema, so the baseline of 3 applies. The description adds nothing about the limit/row-cap semantics beyond what the schema already carries.

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?

States a specific verb and resource ('Get the user's tenant(s)') and enumerates exactly what is retrieved: quotas, billing tiers, recurring charge, trial start, and payment provider. No sibling tool covers tenants, so the agent can select it unambiguously.

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?

Usage is only implied — the agent can infer this is the tenant/account-info lookup, but the description never states when to reach for it versus other get/list tools, nor any prerequisites. There is no explicit alternative named, so this lands at minimum viable.

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