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

With no annotations, the description must carry the burden of behavioral disclosure. It only mentions optional filtering by tag value but does not state whether the operation is read-only, describe the output format, or disclose any other behavioral traits such as default behavior or side effects.

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, somewhat convoluted sentence. It is short and not overly verbose, but the structure is run-on and could be clearer. The information is packed awkwardly, reducing readability.

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?

The tool has no output schema and no annotations, so the description must provide complete context. It lists some return fields (name, best for, tags) but fails to explain the output format, pagination, or the exact behavior of the filter. An agent would not know what to expect from a call.

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 provides no description coverage for filterKey or filterValue. The description mentions filtering by a tag value but does not explain what filterKey should be (e.g., 'tag'), the expected format of filterValue, or any constraints. This is insufficient for an agent to correctly populate the parameters.

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 identifies the resource ('Types of freight intermediary') and the fields returned (name, what it is best for, tags), but it lacks a clear action verb and is awkwardly phrased ('what each does comparison'). It doesn't clearly state that the tool lists or compares options, making the purpose somewhat vague.

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 is provided on when to use this tool versus sibling tools such as compare_criteria or compare_table. The description does not mention any context, exclusions, or alternative selection criteria.

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