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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds genuinely new operational context the annotations cannot express: 'No authentication required' and that access details (OAuth or API token, starter credits) are returned. It does not mention rate limits or response shape, but with no output schema that gap is minor for a static info 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?

Three sentences, front-loaded with the most decision-relevant fact (no auth required), then content scope, then the routing rule. The long comma-separated enumeration of section contents partially duplicates the enum, but each item is informative rather than 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?

For a read-only info tool with no output schema, the description adequately pre-describes the return content and the auth situation. The one omission is guidance on the apparent overlap with the get_pricing sibling, which an agent comparing candidates would want resolved.

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 already documents the single enum parameter at 100% coverage ('Return only one section (default: all)'), which sets a baseline of 3. The description goes further by mapping each section to its content — products and outputs, pricing, commercial license, honest limitations, agent access — giving the enum values meaning the schema alone does not.

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 states a specific verb and resource ('Returns canonical facts about God Mode AI') and enumerates the content categories, so an agent knows exactly what comes back. It differentiates itself from siblings through the routing line about calling it first when evaluating fit, though it never resolves the overlap with the sibling get_pricing despite listing 'pricing' as one of its own sections.

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 usage context is provided: 'Call this FIRST when deciding whether God Mode AI fits a user's need or when comparing it with other sprite/animation tools.' That is clear when-to-use guidance. It lacks any when-not or a direct contrast with get_pricing, which covers similar pricing ground, so it stops short of the top score.

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