list_competitor_visibility

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

The annotations already indicate readOnlyHint=true and openWorldHint=false, so the description does not need to restate safety. It adds the scope of what is compared (target brand and tracked competitors), but it does not disclose details like return format, default behavior without a measurement_window_id, or whether it returns data per competitor. This provides limited behavioral clarity beyond the annotations.

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, front-loaded sentence that is concise and free of filler. It efficiently states the action and the subject matter, with no wasted words.

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 and a single undocumented parameter, the description is too minimal to fully equip an agent. It explains what the tool does at a high level but omits details about the expected input and the shape of the output, which are necessary for correct invocation and interpretation. The sibling tools provide context, but the description itself does not.

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 has one parameter, measurement_window_id, with no description and zero schema_description_coverage. The tool description does not mention this parameter at all, leaving its purpose and possible values entirely undefined. Since the coverage is 0%, the description fails to compensate for the missing parameter information.

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 uses the specific verb 'Compare' and identifies the resource as 'AI visibility across the target brand and tracked competitors.' This clearly distinguishes it from sibling tools like get_visibility_overview, which likely focuses on a single entity, and list_prompts, which lists prompts. The tool's core function is unambiguous.

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 implies usage by stating its purpose, but it does not provide explicit guidance on when to choose this tool over alternatives like get_visibility_overview or get_prompt_visibility. There is no mention of exclusions or prerequisites, so the agent must infer from the tool name and context.

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