Sync Property Data

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the asynchronous nature (returns immediately with job ID), the need to monitor progress via another tool, the pagination capability to overcome API limits, default date ranges, and maximum range constraints. It doesn't mention authentication requirements, rate limits, or error handling, but covers most essential operational aspects.

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?

The description is perfectly front-loaded with the core purpose in the first sentence, followed by important behavioral details. Every sentence adds value: pagination capability, date range defaults and limits, and asynchronous execution pattern. There's zero wasted text or redundancy.

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 tool with 5 parameters, no annotations, and no output schema, the description provides substantial context about behavior, defaults, constraints, and the asynchronous workflow. It doesn't explain the return format (though it mentions job ID) or error conditions, but given the schema's excellent coverage and the clear behavioral description, it's mostly complete for agent usage.

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 all parameters thoroughly. The description adds some context about default date ranges (3 months, up to 16 months with explicit startDate) and the pagination benefit, but doesn't provide additional semantic meaning beyond what's in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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?

The description clearly states the specific action ('Fetch Google Search Console search analytics data into a local SQLite database'), identifies the resource (GSC data), and distinguishes it from siblings by mentioning its unique pagination capability and asynchronous job-based execution. It goes beyond just restating the name/title.

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 description provides clear context about when to use this tool (for fetching GSC data with full pagination, default 3-month range, up to 16 months with explicit startDate) and explicitly mentions an alternative tool for monitoring progress (check_sync_status). However, it doesn't explicitly state when NOT to use it or compare it to other siblings like query_gsc_data or sync_all_properties.

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