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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds which data categories are returned, which is useful, but says nothing about authorization scope, missing-tenant behavior, or freshness of lease history.

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?

A single front-loaded clause with no padding; the payload list is the highest-value information and comes first. Slightly terse to the point of being a fragment rather than a sentence, but nothing is wasted.

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?

An output schema exists, so return structure needn't be re-explained, and the annotations cover the safety profile. What remains missing is parameter guidance and any usage context against list_tenants and the other get_tenant_* tools, leaving the definition minimally adequate.

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 description coverage is 0% for the single required tenant_id, and the description never mentions it — no id format, source, or lookup semantics. The phrase 'one tenant' weakly implies an identifier is needed but adds no meaning beyond the schema's type.

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 clear verb+resource ('Get Tenant') and enumerates the payload (contacts, phones, addresses, lease history), which distinguishes it from scalar getters like get_tenant_notes or get_tenant_udfs. It does not explicitly name list_tenants as the plural counterpart, so sibling differentiation is only implied.

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?

'Full detail for one tenant' implies the single-entity lookup case versus the list_tenants / get_tenant_* siblings, but no explicit when-to-use, when-not, or alternative is stated. Usage is inferable rather than guided.

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