get_geo_fixes

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the tool returns code/text rather than mutating the site (contrasting with make_site_geo_ready) and that output is tailored to the site's current score and issues. It omits auth/permission needs and rate or cost characteristics, but the read-only, non-mutating nature is conveyed.

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?

Three tight sentences, zero filler, with the purpose and enumerated outputs front-loaded and the prerequisite last. Every sentence earns its place.

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 compensates by naming exactly what is returned (four artifact types). For a one-parameter read tool with a stated prerequisite, nothing an agent needs to call it correctly is missing.

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?

Single parameter with 100% schema description coverage, so the schema already documents 'domain' including its example format. The description adds no additional syntax or constraints beyond the schema; baseline 3 applies.

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?

States a specific verb ('Get') and resource ('copy-paste fix instructions for a website's GEO issues') and enumerates the concrete artifacts returned (robots.txt, Organization Schema JSON-LD, FAQ Schema, llms.txt). It also distinguishes itself from siblings by naming analyze_geo_score as the prerequisite and framing it as producing instructions rather than applying them.

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?

Explicit sequencing: 'Call this AFTER analyze_geo_score' and scoping to 'an existing site'. Clear context for when to invoke it, but it stops short of naming when-not to use it or pointing at make_site_geo_ready as the alternative for actually applying fixes.

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