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

The annotations already establish that this is a safe read-only operation. The description adds that it uses GET and that included related records are requested via the include parameter, but it does not mention behavior for missing records, permissions, or response shape beyond the embedded includes.

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 two compact sentences with the primary operation front-loaded. Every sentence contributes useful information and there is no 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 read-only tool with full schema coverage and clear annotations, the description covers the core behavior and include handling adequately. Minor omissions such as not-found behavior or response envelope details are not critical here.

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 100%, and the description adds little beyond noting that UUID identifies the offer and include controls related records. The schema already documents the UUID format, source, and allowed include values in detail, so baseline 3 is appropriate.

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 states a specific resource and retrieval mode: 'One lettings offer by UUID,' which clearly distinguishes a single-record fetch from list operations. It also names the endpoint. It does not explicitly name sibling alternatives such as street_list_lettings_offers, so it falls short of full sibling differentiation.

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 UUID-based framing implies this is for retrieving a known lettings offer, while listing tools would be used to find one. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative for discovery.

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