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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered externally. The description adds that results include "company details with links to their ARCAT profile," which is useful return context, but with an output schema present this is only marginal added value.

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 sentences with zero filler: the search capability is front-loaded and the return note follows immediately. Every clause earns its place.

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 full schema coverage, rich annotations, and an output schema handling return values, the description carries only light burden. It adequately covers what the tool does and roughly what it returns; the missing piece is routing guidance relative to the sibling search/lookup tools.

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 limit, offset, query, csi_section, and csi_division with examples. The description loosely maps its "name, keyword, or CSI MasterFormat section" phrasing onto the query and CSI parameters but adds no syntax or format detail beyond the schema; baseline 3 applies.

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 and resource ("Search for building product manufacturers") and enumerates the searchable dimensions: name, keyword, and CSI MasterFormat section. It does not differentiate itself from the sibling get_manufacturer (single lookup) or search_products, so it falls short of a 5.

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?

Search context is implied by the verb and the listed search modes, which tells an agent this is the broad discovery tool. However, there is no explicit when-to-use guidance, no mention of when to prefer get_manufacturer for a targeted lookup, and no alternatives or exclusions named.

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