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

No annotations are provided, so the description carries the full burden, but it only states the basic operation. It does not disclose whether the comparison is read-only, what data it returns, whether any side effects or permissions are involved, or edge-case behavior such as invalid slugs.

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?

The description is a single four-word sentence with no filler, and the core action is front-loaded. It earns its place, though it is so terse that it sacrifices explanatory depth.

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 one-parameter tool the input contract is reasonably clear, but with no output schema and no annotations the agent is left to guess what 'compare' actually returns and how to interpret the result. Basic invocation is possible, but the definition is not fully complete.

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 schema has a single required 'slugs' array of strings with no property descriptions, and the description adds the minimal clarification that these are product identifiers used for comparison. This is enough for a very simple parameter, but no constraints, format, or examples are provided.

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 names a specific verb ('compare') and resource ('products') and identifies the input key ('slug'), which sets it apart from the sibling compare_companies. It is clear enough to know what operation is performed, though it doesn't specify what aspects of products are compared or what the result looks like.

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?

No guidance on when to use this tool versus siblings like get_pricing, get_company, or compare_companies. The only hint is the tool name and the phrase 'by slug'; there is no explicit context, condition, or exclusion to route an agent.

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