List posts from any platform

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable behavioral context: multiple discovery methods (sitemap, JSON list, Ghost API), bypassing discovery with urls, return fields, and filtering. No contradictions.

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 well-structured into two paragraphs: how it works and when to use. It is concise but could trim some redundancy, e.g., 'Discover posts via...' and 'Pass an explicit urls[]...' are clear but slightly wordy.

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 (multiple discovery methods, 5 parameters, output schema present), the description covers discovery modes, filtering, and return metadata. It provides enough context for an agent to select and invoke correctly.

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 high (80%). The description adds meaning by explaining the fallback environment variables for sitemap_url and the 'since' and 'min_age_days' filters. It goes beyond the schema by describing how urls bypass discovery, which is not in the schema.

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: 'Discover posts via an XML sitemap...' listing posts from any platform. It also distinguishes itself from sibling tools like snapshot, verdict, etc., by focusing on discovery and eligibility.

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?

Includes a 'When to use' section that explains the tool's role in discovering URLs for downstream analysis. It provides clear context but lacks explicit instructions on when not to use it or alternatives besides the implied different purposes of siblings.

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