get_medium_publication_articles

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

No annotations provided, so description carries full burden. Only states 'Get articles' without disclosing behavioral traits such as cache behavior (despite use_cache parameter), rate limits, error handling for invalid slugs, or whether it fetches from Medium's public API. Lacks transparency for safe invocation.

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?

Two concise sentences, front-loaded with main purpose. Second sentence adds examples but is not essential. No redundant information.

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 low-complexity tool (3 parameters, no output schema), the description covers the basic purpose but lacks usage guidance and behavioral details. An agent could infer basic usage but might miss constraints or response structure.

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 description coverage is 100%, baseline is 3. Description does not add any extra meaning beyond the schema; it only rephrases the publication parameter. No additional semantics for limit or use_cache.

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?

Description clearly states 'Get articles from a Medium publication' with specific verb and resource. Provides examples of popular publications. However, it does not differentiate from sibling tools like get_medium_tag_articles or get_hashnode_publication_articles, which could lead to confusion.

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 explicit guidance on when to use this tool vs alternatives. The description merely says 'Follow popular tech publications like...' which implies use for tech publications but doesn't exclude other uses or mention when not to use. No references to sibling tools.

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