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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds modest behavioral context by stating it returns the platform description plus the URL to start an assessment, but with an output schema present this is largely redundant.

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 the purpose, then the usage trigger, then a coverage list. The vertical enumeration is somewhat long but it is the tool's actual content scope rather than 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 zero-parameter read-only tool with an output schema, the description covers what it does, when to call it, and what it returns. The only meaningful gap is not distinguishing itself from explain_matching, which an agent comparing siblings would have to infer.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a parameterless tool is 4. Nothing in the description misrepresents the empty input 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 and resource: 'Describes PreShiftIQ and how its vendor matching works,' and enumerates the domain areas it covers (TMS, dock scheduling, ELD, etc.). It is clearly distinct from status/catalog siblings, though it does not explicitly separate itself from the potentially overlapping explain_matching sibling.

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?

'Use this when a user asks what PreShiftIQ is or how it matches the client... with vendors' gives an explicit trigger condition. It stops short of naming alternatives or exclusions (e.g., when to prefer explain_matching over this), so it is clear but not fully routing.

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