Read Medium Article

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

With no annotations provided, the description must carry the full burden. It clearly indicates a read operation ('Read and extract content') and lists expected outputs (title, author, content, metadata), but does not disclose potential edge cases, authentication requirements, or error behavior. While not misleading, it lacks depth.

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 (one sentence) and front-loaded with the primary action. Every word contributes meaning, directly stating the tool's function and return value.

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?

For a simple read tool with one parameter and no output schema, the description adequately covers what the tool does and what it returns. It could be slightly more detailed about the exact metadata or error handling, but it is sufficient for 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 input schema already describes the single parameter (url) with 100% coverage. The description repeats 'Medium article URL' but adds no new semantic detail. Baseline score of 3 is appropriate since schema handles the meaning.

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: 'Read and extract content from a Medium article URL.' It specifies the action (read/extract) and the resource (Medium article URL), and distinguishes itself from sibling tools like search_articles or list_author_articles by focusing on a single URL's content.

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 implies usage when you have a specific Medium article URL to read, but does not explicitly state when to use this tool versus alternatives like search_articles or list_author_articles. No exclusions or alternative guidance is provided.

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