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

With no annotations, the description carries the full burden and does well: it discloses the per-record fields, the 'total'/'total_at_least' count semantics, truncation behavior, and that output passes through the conversation (a token-cost warning). It omits auth/permission requirements, but the read-only nature is unambiguous.

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?

Dense but well front-loaded: purpose first, then selection modes, then the caveat about output size. Every sentence carries content, though the single long paragraph packs several distinct concerns together.

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?

No output schema exists, so the description must cover returns — and it does (_key, _ts, total, total_at_least, truncation). For a 9-parameter read tool this is nearly complete; only the absence of any permission/auth note keeps it from a 5.

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 100%, so the schema already documents every parameter and the baseline is 3. The description reinforces the selection strategy ('indexed, fast' prefix, truncation to max_chars) but adds little syntax or meaning beyond what the schema descriptions already state.

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+resource (read records of a Scrapy Cloud collection) and immediately characterizes the returned data ('_key' and '_ts' write time). It is trivially distinguishable from siblings like scrapy_cloud_delete_collection_records and scrapy_cloud_put_collection_record, which mutate the same resource.

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?

Explains the selection modes (exact keys, prefix, write-time window) and, crucially, warns that beyond a small sample the caller should use the storage REST API instead — an explicit when-not-to-use rule. It doesn't route to any sibling MCP tool by name, so it falls just short of a 5.

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