list_recommendations

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

The annotation readOnlyHint=true already covers the safety profile, and the description adds ordering behavior and content type. However, it doesn't disclose how parameters like limit, status, or category affect results, nor what the response structure looks like beyond the ordering.

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 description is a single, tight sentence with no extraneous wording. It efficiently states the core purpose and ordering, though its brevity borders on under-specification rather than conciseness.

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?

Given three parameters, no output schema, and minimal annotations, the description is incomplete. It provides a high-level purpose but lacks detail about parameter semantics, return format, or how this tool fits among the sibling tools, making it insufficient for reliable invocation without additional context.

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 0% and the description provides no information about the three parameters (limit, status, category). With the description failing to compensate for the complete lack of parameter documentation, the agent has no basis beyond parameter names to infer their expected values or behavior.

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 identifies the tool as returning AI visibility optimization recommendations ordered by priority, making the resource and scoping clear. However, it lacks an explicit verb like 'list' or 'get,' relying on the tool name for that, and it doesn't explicitly distinguish from sibling tools such as get_visibility_overview.

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 guidance on when to use this tool versus alternatives. The description only states the output ordering ('highest priority first') and gives no contextual cues about prerequisites, filtering, or whether other tools should be preferred for specific scenarios.

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