Get Article Recent

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the inclusive date bound and the return shape (metadata + full wikitext), and 'Retrieve' implies a read operation, but it says nothing about permissions, rate limits, or behavior when no revision exists at/before the date.

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 tight sentences with the scope and result front-loaded and no filler. The trailing return-shape clause is slightly redundant since an output schema exists, but it is brief and harmless.

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?

A read tool with a full output schema and 100% parameter coverage needs only light prose, which this supplies. The main gap is the absence of any pointer to sibling tools (initial/history) that an agent would need to pick the right one.

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%, so the schema already documents all three parameters, making the baseline 3. The description adds only marginal meaning by restating the inclusive upper-bound semantics of date_limit ('at or before'), which the schema already conveys as 'Upper date bound'.

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?

States a specific verb (Retrieve) and resource (latest revision of an article) with an added scope constraint (at or before date_limit). An agent can infer it differs from get_article_initial and get_article_history, though the description never names those siblings explicitly, so differentiation is implied rather than stated.

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 phrase 'latest revision ... at or before date_limit' implies when the tool is appropriate (getting the most recent version bounded by a date), but there is no explicit when-to-use, when-not-to-use, or named alternative. Usage must be inferred from the scope wording.

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