Get pipeline stats

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

With no annotations, the description carries the full burden. The verb 'Fetches' implies a read-only operation, and listing the specific stats (sources checked, posts read, etc.) provides clear behavioral expectations. It also notes the 'most recent run' limitation, which is useful. It omits potential empty-state or auth details, but for a simple getter this is acceptable.

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, well-structured sentence, front-loaded with the verb and resource. It wastes no words and every element adds specific value.

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 tool's simplicity (zero parameters) and lack of an output schema, the description sufficiently covers what the tool does and what data it returns. Enumerating the stat fields essentially serves as the return value documentation.

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 tool has zero parameters, so the baseline is 4. The description adds meaningful context about what the stats represent, which is helpful despite there being no parameter definitions to clarify.

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 a specific action ('Fetches stats') on a well-defined resource ('most recent ingestion pipeline run') and enumerates the exact data returned, which clearly distinguishes it from sibling tools focused on trends and digests.

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 establishes clear context: it is for retrieving stats from the most recent ingestion pipeline run. It does not explicitly mention alternatives or when-not-to-use, but the purpose is so distinct from siblings that the context is sufficient.

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