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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the default sort ('Newest first as Street orders them') and pagination mechanics plus the field shape of a lead, but says nothing about the deleted-record behaviour or result volume, which are real behavioural concerns for a paged list.

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?

Three short sentences, front-loaded with the purpose and resource definition before ordering and paging details. Only 'page with page and page_size' is close to restating the schema, but it functions as usage guidance.

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, 10-optional-parameter list tool with no output schema, the definition covers purpose, ordering, paging and record shape. It leaves out any mention of the filtering power (branch, created/updated ranges, email, phone) and the deleted-record mode, but those are fully documented in the schema, so nothing critical is missing.

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 ten parameters are documented in the schema itself, including the 'trashed' semantics and the sync hint on updated_from. The description only restates page/page_size, adding no semantics the schema lacks; baseline 3 applies.

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 (List) and resource (enquiries), and defines the resource inline as 'inbound leads: who, which property, message, source', which separates it from unrelated list_* siblings such as street_list_tasks or street_list_invoices. It does not explicitly phrase the contrast with street_get_enquiry (single record), though 'List' carries that distinction.

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?

Gives concrete pagination guidance ('page with page and page_size'), but never says when to reach for this tool versus street_get_enquiry or the other list endpoints, and does not surface the filter dimensions (branch, date ranges, email/phone) that determine whether it fits a given query.

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