extract_article

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

The description declares read-only behavior, no external modifications, and discloses authentication requirements, rate limits, and error triggers. With no annotations, this fully informs the agent of critical behavioral constraints.

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 and well-structured, front-loading the core purpose and progressively adding usage guidance, behavioral details, and constraints 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?

The description fully informs the agent: clear purpose, usage alternatives, return fields (despite no output schema), prerequisites, rate limits, and error states. No gaps remain given the tool's complexity.

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 covers the parameter fully (100% coverage), but the description adds value by clarifying the URL must be HTTP/HTTPS and specifying best-use cases, slightly exceeding the baseline.

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 extracts main article content from news articles, blogs, or editorials, and explicitly distinguishes it from the sibling tool 'extract_url' by specifying when to use each.

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 explicit when-to-use guidance ('Use this instead of extract_url when you specifically need article content'), works-best scenarios, and notes prerequisites (HAUNT_API_KEY), rate limits, and error conditions.

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