get_zone_recent_scans

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

With no annotations provided, the description carries the full behavioral burden, yet it only implies a read via 'Get'. It does not define the 'recent' window, whether results are paginated or capped, what permissions are required, or what the response contains. Useful context beyond the name is essentially absent.

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 tight sentence with the verb and resource front-loaded and zero filler. It is efficient, though 'recent' is left vague where a brief qualifier would have earned the space.

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 read tool with no output schema and no annotations, this is minimally adequate: an agent can invoke it, but the undefined recency window and the missing distinction from get_account_recent_scans are real gaps. Some additional context would materially improve routing accuracy.

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% and the single zone_id parameter is fully described in the schema, so the baseline 3 applies. The description adds nothing about the parameter — not its format, source, or whether it accepts a name in place of an ID.

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 ('Get') and resource ('recent Security Center scans') scoped to 'a Cloudflare zone', so the operation is unambiguous. However, it never distinguishes itself from the near-identical sibling get_account_recent_scans, leaving the agent to infer the zone-vs-account scope difference from the name alone.

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 when-to-use guidance, no prerequisites, and no mention of the account-level sibling that a caller could easily confuse this with. The agent is given no condition that selects this tool over get_account_recent_scans.

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