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

Mentions neutrality, factual accuracy, and source attribution, which are behavioral guarantees. However, with no annotations, it lacks explicit mention of side effects, auth, or rate limits, though the tool is likely read-only.

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?

Concise, two sentences plus a tip and context note. Front-loaded with the main action and outputs.

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?

Covers main behavior and mentions source attribution, but doesn't describe return format or edge cases. Given no output schema, it's reasonably complete for a simple summarizer.

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 implies the four parameters (url, html, text, length) but gives no formal definitions or constraints. It mentions 'short, medium or long' for length but doesn't document allowed values or interactions between inputs.

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?

Clearly states the tool summarizes input content (URL, text, HTML) at a requested length. Though it doesn't explicitly contrast with sibling tools, the verb and resource are specific enough to distinguish it.

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?

Provides a sample endpoint and notes it's part of a content kit, but does not specify when to choose this over other tools like extract_structured or detect_language. No explicit guidance on use cases or prerequisites.

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