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

Annotations already declare readOnlyHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: sort order, the fields surfaced per item, and the operational warning that service of process is time-critical and should be surfaced prominently. It omits any mention of pagination behavior despite pageSize/pageToken parameters.

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 tight sentences, front-loaded with what the tool returns and followed by the one piece of operational judgment an agent needs. No redundant restatement of the title or annotations.

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-shape explanation is not required, and the description covers content and priority well. However, with two undocumented pagination parameters and a nested companyId object, an agent lacks guidance on how to page through results or what the size limit means.

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 only 33%: companyId carries a generic 'UUID value wrapper' note and pageSize/pageToken have no descriptions at all. The description's phrase 'as the company's registered agent' hints at the companyId scope but does not explain paging or limits, so it fails to compensate for the coverage gap.

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 ('Lists the mail Lovie has received as the company's registered agent') plus ordering ('newest first') and returned attributes ('what kind each item is and whether it has been passed on'). This is clearly distinct from registeredagent_list_requests or registeredagent_get_request, though no sibling is named explicitly.

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 context implies when to call it (to review incoming registered-agent mail), and the second sentence gives presentation guidance about elevating service of process. It never says when to prefer registeredagent_list_requests or registeredagent_get_request instead, so selection guidance is left to inference.

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