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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, but the description adds genuinely new behavioral facts: a durable daily reservation that repeated calls cannot bypass, an hourly schedule sharing that reservation, and 24-hour retry with preservation of the last good sample on failure. These rate-limit and failure-recovery semantics are exactly the kind of context annotations cannot express.

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 action is front-loaded in the first sentence, but the last two sentences are near-duplicates of the reservation point: 'Repeated calls cannot bypass the daily reservation' and 'This route cannot force an extra collection' say the same thing twice. Trimming that redundancy would sharpen the definition.

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?

With no output schema, the description should explain more about what a run produces or returns, and what 'sample' means in this domain. It does cover scheduling and failure behavior well, but leaves the agent without a clear picture of the operation's outcome or its connection prerequisite.

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% — the single 'id' parameter is documented as 'Site ID from list_sites or add_site.' The description contributes no additional meaning about the parameter, 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?

The description says it will 'collect a due sample', which names an action but uses opaque jargon rather than stating that it syncs Search Console data. The resource is unclear and it does not differentiate itself from siblings such as search_console or connect_search_console. An agent can infer intent from the tool name but not confirm it from the text.

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 implies a when-not condition ('cannot force an extra collection', 'cannot bypass the daily reservation'), which tells the agent not to expect this route to trigger an unscheduled collection. However, it never states when to prefer this over search_console or connect_search_console, or what preconditions exist.

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