pipeline_status

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, and it discloses almost nothing: no indication of whether the counts are live or cached, how fresh 'Last run' is, or whether the call is read-only. For a zero-param status tool the safety profile is low-risk, but the reporting semantics (snapshot vs. live, units, time windows) remain entirely undisclosed.

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?

It is a single telegraphic fragment list with no wasted words, so it is certainly concise. However, it is under-specified rather than well-structured: there is no sentence structure, no verb, and the four comma-separated items read as raw field names without framing.

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?

An output schema exists, so the description need not enumerate return values, and with no parameters the input surface is trivially complete. Still, a 16-sibling server with no annotations warrants at least a word on when to consult this status tool and whether the numbers are point-in-time, which is absent.

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 takes zero parameters, so there is no parameter meaning for the description to supply. Baseline 4 applies; nothing here misleads about inputs.

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 fragment list identifies the resource (pipeline status: last run, OpenAlex daily calls, PDF parse counts, seed count) but never states an action verb or that the tool returns these values. An agent can infer it is a read of pipeline health metrics, but must lean on the tool name to do so. It is distinguishable from siblings only because none of them deal with pipeline metrics.

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 guidance on when to call this tool, what triggers it, or how it relates to siblings like ensure_workspace or list_seeds. The agent is left to guess that this is a diagnostic/health-check tool consulted before or after running the pipeline.

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