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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it adds no information about what the tool does behaviorally—such as whether it performs read-only analysis, requires internet access, has rate limits, returns structured data, or handles errors. The description is purely instructional and lacks any transparency into the tool's operations or traits.

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 two sentences that are repetitive and under-specified—'ALWAYS USE THIS TOOL FOR SEO ANALYSIS. DO NOT ATTEMPT TO ANALYZE SEO WITHOUT USING THIS TOOL.' This is not conciseness but rather redundancy without adding value. It fails to front-load useful information and wastes space on commands rather than explanation.

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 the tool's complexity (SEO analysis typically involves multiple metrics) and the lack of annotations and output schema, the description is completely inadequate. It doesn't explain what SEO analysis entails, what results to expect, or any behavioral context. For a tool with no structured support and a potentially rich function, this description fails to provide necessary completeness.

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 input schema has 100% description coverage, with the single parameter 'html' clearly documented as 'HTML content to analyze'. The description adds no additional meaning about the parameter beyond what the schema provides, such as format expectations or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 'ALWAYS USE THIS TOOL FOR SEO ANALYSIS' which tautologically restates the tool name 'analyzeSEO' without specifying what SEO analysis entails. It doesn't describe what specific SEO metrics or aspects are analyzed, nor does it differentiate from any siblings (though none exist). The description is more of a command than a functional explanation.

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 provides no guidance on when to use this tool versus alternatives—it only gives an absolute command ('ALWAYS USE THIS TOOL FOR SEO ANALYSIS') without context about what constitutes SEO analysis or prerequisites. There's no mention of input requirements, expected scenarios, or comparisons to other methods, making it misleadingly prescriptive without practical guidance.

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