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

No annotations are provided, so the description carries the full behavioral burden and delivers little: nothing about invalid-slug handling, whether the underlying tools are read-only or mutate anything, error semantics, or rate limits. The passthrough 'input' object's behavior is likewise undisclosed.

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 first sentence front-loads the dispatch purpose, and the slug enumeration is necessary given the schema has no enum constraint. It is dense and earns its length, though the flat comma list could be grouped by category for faster scanning.

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?

For a generic dispatcher wrapping 16 heterogeneous tools with a free-form nested input object, no output schema and no annotations, the description omits how 'input' should be shaped per tool, what comes back, and how failures surface. An agent can identify the tool but cannot confidently invoke it.

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 coverage is 0% and the 'tool' property is a bare string, so the description's enumerated slug list is genuinely valuable and compensates for that gap. However, the nested 'input' object (additionalProperties: true) is left entirely unexplained, so half the surface remains undocumented.

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 ('Run') and resource ('any MarsGeo SEO tool by slug') and enumerates the 16 supported slugs, so an agent knows exactly what dispatch surface this covers. It stops short of distinguishing itself from the eight sibling generate_* tools, which overlap almost one-for-one with the listed slugs.

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 statement of when to use this generic dispatcher versus the dedicated siblings (generate_faq_schema, generate_sitemap, validate_json_ld, etc.). The slug list implies capability but leaves the routing decision entirely to inference, which is costly given eight near-duplicate alternatives.

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