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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by noting digests are opt-in and default off, and by naming the threshold and email override fields, effectively providing the return contract in the absence of an output schema.

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?

One efficient sentence that front-loads the resource and includes only valuable details in the parenthetical. No filler or repetition of schema facts, so every part earns its place.

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 read tool with full annotation coverage and no output schema, this description is sufficient: it names every meaningful piece of returned configuration and makes the input scope clear. Nothing needed to call the tool correctly is missing.

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?

The schema already documents site_id as a logical RankParse website ID sourced from list_rank_tracking_sites, so parameter coverage is complete. The description only reinforces the singular 'one RankParse website' scope and adds no new constraints or format details, making the schema-carrying baseline of 3 appropriate.

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 ('rank-change alert configuration for one RankParse website'), then enumerates the exact fields returned: digest enabled state, moved_up/moved_down threshold, and digest email override. This clearly distinguishes it from sibling tools like update_rank_alert_settings and list_rank_change_alerts.

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 makes clear this is a read operation scoped to a single RankParse website and describes what the caller will receive. It does not explicitly mention when to prefer it over update_rank_alert_settings or list_rank_change_alerts, but the context is clear and there are no misleading exclusions.

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