get_article

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

Without annotations, the description carries the full burden. It mentions it's a public GET endpoint and that id is needed for update/delete, but does not discuss rate limits, authentication details, or side effects beyond saving to file. Adequate but not exhaustive.

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 a single, information-dense sentence that front-loads the main purpose and lists key fields. It is concise with no wasted words, though it could benefit from slight structuring for readability.

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 no output schema, the description lists many returned fields but not all. It mentions dates but not their format. The site parameter is missing. The saveToFile hint for large articles adds practical guidance. Overall, moderately complete but with a notable gap.

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 clarifies the slug parameter (used as identifier) and the saveToFile parameter (path to write JSON, returning summary in chat). However, the site parameter is not explained, and schema description coverage is only 33%. The description partially compensates for low schema coverage but misses one parameter.

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 that the tool retrieves the full article by slug, listing the fields returned (title, content, excerpt, etc.) and distinguishing it from sibling tools like delete_article and update_article by mentioning that the returned id is needed for those operations.

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 for fetching full article content by slug, but does not explicitly state when not to use it or offer alternatives. Context from sibling tool names like list_articles suggests when to use those, but the description itself lacks direct guidance.

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