Export Search Console reports

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 concrete side effects (writes CSV, report.json, summary.md), the exact save location (.gsc-reports/), and the .gitignore modification, plus a previous-period comparison. It stops short of mentioning auth/permission requirements, overwrite behavior, or rate limits.

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?

Front-loaded with the verb 'Download' and contained in a single dense sentence with no filler. The enumerated lists are informative rather than redundant, though the compound sentence is somewhat heavy.

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?

Given no output schema, the description compensates well by spelling out the three output artifacts and their contents. For a 4-param, zero-required tool it covers the deliverable fully, missing only prerequisite/auth context.

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 75%, so the schema largely documents days, type, siteUrl, and allSites itself. The description mentions none of these parameters and adds no syntax or default meaning beyond what the schema already provides, so the baseline of 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+resource ('Download Search Console reports') and enumerates the exact report types and file formats produced, so the agent knows precisely what this yields. It does not name the nearest siblings (gsc_search_analytics, gsc_performance_summary) to contrast against, keeping it just 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?

The phrase 'in one step' implies bulk/at-a-glance export versus a single query, but there is no explicit when-to-use or when-not-to-use guidance and no routing away from gsc_search_analytics or gsc_performance_summary. Usage is only implied.

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