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

The description adds no behavioral details beyond the annotations. It does not mention potential errors, return format specifics, or any side effects, relying entirely on the minimal annotations.

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 very concise with a single sentence, which is good, but it omits essential information, making it under-specified rather than appropriately succinct.

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 simple nature of the tool, the description still lacks sufficient context to distinguish it from sibling tools and to understand the expected input/output relationships. It does not mention the article format details beyond 'Markdown' or how the section and slug uniquely identify an article.

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 repeats the enum values for `section` but does not explain the `slug` parameter or how the two parameters interact. The schema itself has no parameter descriptions, so the tool description provides only partial semantic coverage.

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 states that the tool returns 'one article as Markdown' and lists the valid sections, but it lacks a clear verb or explicit statement that it retrieves an article by slug and section. The noun-phrase style leaves some ambiguity about the action.

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?

No guidance is provided on when to use this tool versus siblings like get_page, list_articles, or get_provider. The description does not mention alternative tools or selection criteria.

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