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

Annotations already declare readOnlyHint: true and destructiveHint: false, so the read-only nature is known. The description adds useful context about being a follow-up to a previous search and how offset is calculated, but does not detail return format or edge cases, which is acceptable given the annotations.

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 sentences, front-loaded with the purpose, then usage instructions. Every sentence earns its place with no unnecessary words.

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 pagination tool with no output schema and a complex parameter set, the description covers the key context: prior result dependency, trigger phrases, and offset meaning. Minor omissions like default limit or return structure are not critical since the tool is essentially a paged version of search_companies.

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 9% (offset is described), but the description compensates by telling the caller to pass the same criteria as the original search, giving all 11 parameters collective meaning. It specifically explains offset as 'number of companies already shown', which is crucial for correct usage.

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 clearly states 'Load more companies from a previous search_companies result' with a specific verb and resource. It distinguishes itself from the sibling search_companies and load_more_contacts by targeting pagination of company results.

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?

Explicitly lists trigger phrases ('show more', 'load more', 'more companies') and instructs to pass the same criteria plus offset. It implies a prerequisite of a prior search but does not explicitly call out when not to use or name alternative tools, so it falls short of a 5.

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