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

No annotations are provided, so the description carries the full burden. It discloses the returned fields, which implies a safe read-only listing, but says nothing about pagination, project scoping, or auth requirements for a tool with zero annotation coverage.

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?

Two tight sentences, front-loaded with the primary action and return shape, then the usage routing. No wasted language.

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 two-parameter list tool with no output schema, the description covers the action, return fields, and usage context adequately. Minor gaps remain around pagination and whether results are scoped or limited.

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 description coverage is 100%, so the schema already documents both 'project_id' and 'search' (including case-insensitive matching). The description's note that the spider name maps to 'id' is useful but concerns output, not input parameters, so the baseline 3 applies.

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 ('List the spiders deployed in a Scrapy Cloud project') and enumerates the returned fields (name/'id', tags, type, deployed version). This clearly differentiates it from siblings like scrapy_cloud_list_jobs or scrapy_cloud_list_collections.

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?

Explicitly routes the agent: use it to find the spider name before scrapy_cloud_run_spider or scrapy_cloud_create_periodic_job. Clear context and downstream alternatives, though it offers no explicit 'when not to use' or exclusion conditions.

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