:

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

No annotations are provided, placing full burden on the description. While 'Fetch' implies read-only, the description fails to explain the three boolean flags (save_artifacts, crossref_validate, include_bibtex) which clearly modify behavior, or disclose what the payload contains, caching behavior, or rate limits.

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 single sentence is front-loaded with the essential operation and contains no waste. However, given the parameter complexity and lack of schema support, this brevency borders on under-specification rather than ideal conciseness.

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 tool with 4 parameters (3 undocumented in schema), no annotations, and no output schema, the description is insufficient. It fails to explain the behavioral flags, return value structure, or prerequisite conditions (e.g., authentication implications given sibling 'oe_auth_status').

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?

With 0% schema description coverage, the description must compensate for all four parameters. It only contextualizes 'article_id' via 'by article id', but completely omits the three optional boolean parameters (save_artifacts, crossref_validate, include_bibtex), leaving their semantic purpose and side effects undocumented.

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 provides a clear verb ('Fetch'), resource ('article payload'), and identification method ('by article id'). However, it fails to differentiate from siblings like 'oe_ask' (which likely queries articles) or 'oe_history_list' (which lists articles), leaving ambiguity about when to use ID-based retrieval versus other access patterns.

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 offers no guidance on when to use this tool versus alternatives. Given siblings like 'oe_ask' (likely for querying) and 'oe_history_list', the agent needs explicit signals about when ID-based fetching is preferred over searching or browsing history.

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