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 two useful behavioral facts beyond that: the response shape (id, name, email, phones) and the underlying call (POST agents/search, i.e. POST despite being a read). It does not disclose match semantics (exact vs partial, AND vs OR across filters), which matters for a search tool.

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, zero filler, with the search capability front-loaded and the return fields immediately after. Nothing repeats the schema 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?

With no output schema, the one-line return summary ('id, name, email and phones') is genuinely valuable and covers the main gap. However, for a 5-parameter search tool with 40% schema coverage and no required params, the description should state matching behavior and whether filters are ANDed — an agent could otherwise pass an over-broad query and misread the results.

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 coverage is only 40% — limit and phone are documented, while email, first_name and last_name have no schema description. The description partially compensates by naming name, email and phone as search keys, but it never explains that 'name' splits into first_name/last_name or how multiple filters combine.

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 ('Search agents') and disambiguates the domain term with '(producers)'. It also enumerates the searchable fields and the returned fields, so it is clearly distinguishable from searches of individuals, groups, or carriers — though it never names a sibling 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?

Usage is only implied: an agent can infer this is the lookup to use when it needs an agent's id before calling agencybloc_get_agent or a create tool. There is no explicit when-to-use/when-not, no prerequisite note, and no routing to alternatives like agencybloc_search_individuals for people who are not producers.

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