seo_geo_check

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does a good job by explicitly listing what the tool analyzes, including AI crawler access, robots.txt rules, JS rendering, content structure, citation readiness, and FAQ/entity extraction. It does not explain live-fetch behavior or how optional html and robotsTxt inputs affect execution, but the 'Check' and 'Analyzes' wording clearly indicates a non-mutating inspection tool.

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 well-structured and front-loaded with a clear one-sentence purpose, followed by a concise bulleted list of analysis dimensions. It ends with a one-line statement of business value that justifies relevance. Every line contributes useful information without redundancy or filler.

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?

The description provides strong context about what the tool checks, why it matters, and where it fits in the GEO landscape, which is sufficient for selecting it. It does not describe expected return values, but with no output schema and no annotations, that is a minor gap. It also does not explicitly discuss how optional html and robotsTxt parameters are used, but the parameter names and schema descriptions are self-explanatory enough.

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%, so the baseline is 3 and the schema already documents all parameters. The description adds some thematic meaning by mentioning robots.txt rules and JS rendering, which relate to robotsTxt and html, but it does not clarify the relationship or precedence between required url and optional html/robotsTxt inputs. The added semantic value over the schema is modest.

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 clearly states the verb 'Check' and the resource: whether a website is optimized for AI search engines (GEO). It further specifies the analysis areas, making the tool's purpose concrete. However, it does not explicitly distinguish itself from the sibling tools seo_ai_crawlers or seo_robots_ai, which likely overlap in checking AI crawler access and robots.txt rules.

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 when to use the tool by noting it is 'Critical for visibility in ChatGPT, Perplexity, Claude, and Gemini responses.' It does not explicitly state when to prefer this tool over seo_ai_crawlers or seo_robots_ai, nor does it provide any when-not-to-use conditions. The guidance is present but left mainly to inference.

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