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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds real context beyond that: results are alphabetical, they are coverage-only with no participation status, and the response includes an assessment-start URL.

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, front-loaded with what the tool returns and its scope, then usage, then return contents. Efficient, though the parenthetical about the client and assessment adds a slightly heavy clause that could be trimmed.

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?

Covers purpose, scope boundaries, when to use, and a note about returns; an output schema exists so return values need no further explanation. The only gap is that the single parameter is never explained in prose, which is minor given the enumerated values.

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 0%, so the description carries the burden, yet it only says 'one vertical' without naming vertical_id or explaining how the enum values (tms, eld, etc.) map to verticals. The self-documenting enum partly compensates, making this adequate but not enriching.

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 (lists vendors PreShiftIQ covers in one vertical) and explicitly scopes it as catalog coverage only, contrasting with client-specific matches that come from a completed assessment. An agent can distinguish this from my_matches without opening the schema.

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?

Gives clear triggering conditions: 'Use this when a user asks which vendors PreShiftIQ covers or whether a named vendor is covered.' It implicitly contrasts with my_matches but never names a sibling tool as the alternative for the other case, so it stops short of explicit routing.

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