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

With no annotations, the description carries the burden and does disclose useful traits: case-insensitive matching, any-cell scope, and a hard 50-row ceiling. It omits whether the operation is read-only (implied), how results are ordered, and whether the cap truncates silently or signals more results exist.

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?

A single sentence that front-loads the resource, then the matching rule, then the cap – no filler and nothing buried.

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 2-parameter read tool with no output schema and no annotations, the definition covers matching and limits but says nothing about the returned shape (row structure, field names) or ordering, which an agent needs to consume the results.

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 50% – 'query' is documented in the schema as 'text to look for in any cell' while 'limit' has only type/bounds. The description adds case-insensitivity for query and restates the 50 cap already implied by limit's maximum, so it contributes modest meaning beyond the 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?

States a specific verb and resource ('Rows of the Send A Parcel Compare dataset whose cells contain the query'), including matching semantics and the 50-row cap, so the agent knows exactly what the tool returns. It does not explicitly contrast itself with siblings like dataset_row or dataset_top, 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?

No guidance on when to use this versus dataset_row, dataset_top, or dataset_columns, and no exclusions or prerequisites. The 'search' framing implies free-text lookup but nothing routes the agent between the sibling dataset tools.

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