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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description usefully adds the dependency relationship (siblings read what this stores) but does not explain the destructive/idempotent behavior — it frames the call as a benign 'pull fresh data,' which understates what an overwriting sync may do.

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 action and its payload, then the operational trigger. Every clause earns its place with no filler.

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 single-parameter tool with no output schema and full annotation coverage, the description covers purpose, usage, and dependency adequately. The only remaining gap is behavioral: it never clarifies what the destructive sync overwrites or how a re-run affects existing stored data.

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 only one required parameter (site_id) exists, so the schema fully documents it. The description adds no syntax or constraint detail beyond what the schema provides, which matches the baseline for full coverage.

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 — pulling fresh Search Console data into XeoRank — and enumerates what is collected (queries, query-to-page mapping, URL inspections). It clearly distinguishes itself from read-only siblings like get_gsc_queries by naming itself as the thing they read from.

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?

Explicit when-to-use: 'Run this FIRST if get_gsc_keyword_candidates, seed_keywords_from_gsc or get_site_journeys come back empty.' It names the dependent alternatives and the triggering condition, leaving nothing to inference.

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