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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so "Read only; no spend" merely repeats structured data. Nothing is said about pagination, return shape, or whether results are account-scoped, which would be the added value here.

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?

Very short and front-loaded with the action, which is good, but the trailing internal URI reference adds no information for an agent and the space would have been better spent on parameters.

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?

No output schema, six parameters including a nested object, and no description of what a sitelink record contains or how results are paginated. The definition is far too thin to call this tool correctly beyond guessing at accountId.

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?

Six parameters with only 50% schema coverage and one nested object, yet the description explains none of them, including the required accountId. The "Fields: soclo://tools/..." pointer is an opaque URI, not parameter meaning.

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?

"List account sitelinks" gives a verb and resource, but it is essentially the tool title restated. It does not scope the operation (which account, what sitelink data) or distinguish this from near-name siblings like soclo_ads_list_account_callouts or soclo_ads_add_account_sitelinks beyond the verb.

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?

There is no statement of when to use this versus the add/update/remove sitelink siblings or the callout/structured-snippet listers. "Read only; no spend" describes safety, not usage conditions.

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