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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the bar is lower; the description still adds real value by disclosing the return shape (id, name, abbreviation, phones) in the absence of an output schema. The "POST carriers/search" note signals that a read is issued via POST, which usefully pre-empts confusion, though it does not mention result-cap or rate-limit behavior.

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 with the purpose and filters front-loaded, followed by return fields and the endpoint. Nothing is padded or repeated.

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, listing the returned fields is the key missing piece and it is supplied; the 3-param, zero-required schema is largely self-documenting. Minor residual gap: matching semantics (exact vs partial, AND/OR between filters) are not stated.

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 67%, so the schema already explains limit (1-500, default 50, no paging) and phone matching. The description only echoes the name/phone filters and says nothing about the limit parameter or whether name and phone are ANDed or ORed, so it does not compensate for the remaining 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 ("Search insurance carriers") plus the two filter dimensions (name, phone), and names the returned fields. It is unambiguous against siblings such as search_agents, search_groups, and search_individuals because the resource (carriers) is distinct and no other carrier tool exists.

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 implies usage by naming the supported filters (name, phone) but never states when to use this versus a get-by-id or list operation, nor does it set exclusions or prerequisites. The critical practical guidance ("no paging: narrow with filters") lives only in the schema, not the description.

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