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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful ordering and pagination context, but does not disclose auth requirements, rate limits, or deeper response behavior.

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 short and front-loaded: resource definition, ordering, pagination, then endpoint. There is no filler, though it could omit the redundant endpoint mention if space mattered.

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 read-only list tool with full parameter schema coverage and rich annotations, the description is adequate: it defines the resource and covers ordering and pagination. It does not explain the return envelope or included-record structure, which matters somewhat because there is no output schema.

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%, so all eight parameters are already documented in the input schema. The description mentions page and page_size, but adds no syntax or filtering semantics beyond what the schema provides; this is the expected baseline when the schema does the heavy lifting.

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 names a specific verb and resource ("List lettings instructions") and defines the domain term as "an agreement to let: property, owner." It does not explicitly distinguish this from the sibling get_lettings_instruction or street_list_sales_instructions, but the resource is still clear.

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?

It states ordering and pagination behavior ("Newest first... page with page and page_size"), which implies this is the list endpoint for browsing lettings instructions. However, it gives no explicit when-to-use guidance versus get_lettings_instruction or the sales-instructions sibling.

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