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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, covering safety. The description adds useful behavior beyond annotations by specifying that results are returned as directory JSON text with listing summaries and readiness information, and that filtering is entirely optional. It does not mention pagination or ordering, but for a read-only browsing tool this is not a critical gap.

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 sentences, each earning its place: purpose and scope, optional filtering, and a pointer to the sibling tool. The information is front-loaded and free of 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 directory tool with 100% schema coverage and full annotation coverage, the description is complete. It explains what the tool returns in the absence of an output schema and clearly identifies when to use nexez_search instead, leaving no critical gap for an agent deciding whether to call it.

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 the schema already documents every parameter and its meaning. The description adds only the general statement that all filters are optional, which is already implied by zero required parameters. It does not add syntax, formatting, or interaction details beyond the schema.

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 verb ('browse') and resource ('published Nexez listings'), and clearly distinguishes itself from nexez_search by noting it does not require a buyer query. It also states the return type (directory JSON text with summaries and readiness information), making the tool's purpose unmistakable.

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 description explicitly says to use nexez_search when ranked matches for a specific buyer request are needed, providing a clear alternative and boundary. It also clarifies that all filters are optional and that browsing requires no buyer query, which tells the agent when this directory tool is the right choice.

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