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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral value by disclosing a data-scoping guarantee: the CMS connection is returned but 'never its credentials.' It does not discuss pagination or freshness, but those are minor for a single-site settings read.

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 sentences, both front-loaded with the payload: the first packs the full content inventory into one scannable clause list, the second handles routing. No filler, no restatement of the tool name or title.

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 compensates by enumerating the returned settings categories, and annotations cover the safety profile. An agent has enough to select and invoke it correctly without opening anything else.

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% and there is a single 'site' parameter, so the schema fully documents the input; the description adds nothing about parameter format or allowed values. Per the high-coverage baseline, a 3 is 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 (read) and resource (site settings) and enumerates the exact content domains returned: business profile, keyword counts, article options, image style, CMS connection, Google/Bing state, indexing and plan status. This distinguishes it from narrow siblings like get_billing, get_indexing_status, and get_notification_prefs.

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?

Explicitly routes the agent to alternatives with conditions attached: 'Change values with update_settings; connect a CMS with connect_platform.' It also marks the read-only nature, so an agent knows not to attempt mutation here. Nothing about when to prefer this over its siblings is left to inference.

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