Pipepost

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully reveals the credit-based tiering system (free basic scoring vs paid full analysis) which is important operational context. However, it doesn't disclose other behavioral traits like rate limits, authentication requirements, response format, or what constitutes 'basic scoring' versus 'full analysis'. The description adds some value but leaves significant behavioral aspects unspecified.

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 appropriately concise at 12 words, front-loading the core purpose ('Analyze content for SEO quality') followed by important operational details about pricing tiers. Every sentence earns its place by providing distinct value. However, the dash punctuation could be cleaner, and it could be slightly more structured for optimal 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?

Given a 2-parameter tool with no annotations and no output schema, the description provides adequate but incomplete context. It covers the core purpose and pricing model but doesn't explain what the output looks like, what metrics are included in 'SEO quality', or how the analysis is performed. For a tool that presumably returns structured SEO assessment data, more detail about the nature of the analysis would be helpful.

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 description coverage is 100%, so the schema already documents both parameters ('content' and 'keyword') adequately. The description doesn't add any parameter-specific information beyond what's in the schema - it doesn't explain how these parameters interact, what format the content should be in beyond 'markdown', or how the keyword influences analysis. With complete schema coverage, the baseline score of 3 is appropriate.

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's purpose: 'Analyze content for SEO quality' specifies both the action (analyze) and resource (content for SEO quality). It distinguishes from siblings like 'seo_meta' and 'seo_schema' by focusing on content analysis rather than metadata or structured data generation. However, it doesn't explicitly differentiate from 'content_audit' which might have overlapping functionality.

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 implied usage guidance by mentioning 'basic scoring is free, full analysis with issues and suggestions requires credits' - this suggests when to expect different levels of output. However, it doesn't explicitly state when to use this tool versus alternatives like 'content_audit' or 'seo_meta', nor does it provide clear exclusion criteria or prerequisites for use.

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