analyze

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

No annotations provided, so the description fully discloses behavior: sequential processing, credit cost per URL, progress reporting, and detailed return values including GEO/AEO score with sub-metrics.

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 concise with two sentences, front-loading the purpose and key details. Every sentence adds value without redundancy.

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?

Given one parameter and no output schema, the description adequately covers the tool's purpose, processing behavior, output contents, and constraints (credit cost). No missing critical information.

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 description adds context beyond the schema (100% coverage) by explaining processing mode and cost per URL. While the schema defines the 'urls' parameter, the description clarifies its usage behavior.

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 tool analyzes URLs for SEO issues, runs all analyzers, and returns scores, issues, and GEO/AEO scores. It distinguishes itself from siblings like get_stored_analysis (retrieves stored), list_analyzers (lists), and scan_domain (domain scan).

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 indicates typical usage: analyzing one or more URLs fully. It mentions sequential processing and progress reporting. However, it doesn't explicitly state when to avoid this tool or provide direct comparisons to siblings.

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