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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful context beyond that: the authentication prerequisite ('Needs the customer's AI Visibility Employee key') and the scope of returned data. It stops short of stating whether the key is per-customer scoping, how errors surface, or cost/latency traits.

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 short sentences with no filler, and the prerequisite is stated up front alongside the payload summary. Front-loading is slightly weakened by leading with a field list rather than the action.

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 does the right thing by enumerating the returned data categories. However, it leaves unresolved how the required key is supplied given there are no parameters, and gives no sense of data freshness or per-customer scoping behavior.

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?

Zero parameters gives a baseline of 4, but the description references a required 'AI Visibility Employee key' that does not exist in the schema, which risks an agent attempting to pass it as an argument. That mismatch slightly undermines an otherwise trivial empty-input tool.

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 is a noun phrase enumerating what the tool reports (channels, languages, mode, guardrails, post counts, best performers) but never states a verb such as 'returns' or 'retrieves'. The specific field list does distinguish it from siblings like amplify_list_posts, but the agent must infer from the name that this is a read/status operation.

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?

No guidance on when to call this versus alternatives such as audit_ai_visibility or amplify_list_posts, and no exclusions. The only conditional content is a prerequisite (needing the customer's key), not usage routing.

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