open_items

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

With no annotations present, the description carries the full burden and discloses almost no behavioral traits. The word 'Every' implies an exhaustive, unfiltered result set, which is a useful hint, but there is no information about ordering, result size, whether the three categories are merged or grouped, or any permission requirements.

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?

A single front-loaded sentence with a colon-delimited enumeration; no filler and no repetition. It is appropriately sized for a zero-argument tool.

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?

There is no output schema, so the description is the only source of return-value information, and it does name the three content categories it aggregates. However, the shape of the result (per-category grouping, counts, node identifiers, severity of the 'open_items' vs the other buckets) remains undefined for a tool whose whole value is the returned list.

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 nothing parameter-level to document; baseline 4 applies. The description does not mislead about any 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?

Names the resource (every open item in the ontology) and enumerates its three constituent categories: open items, unmet gates, and HIGH-severity nodes. That is specific enough to distinguish it from a single-node lookup or a gate check, though no sibling is named explicitly as an alternative.

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?

There is no statement of when to use this tool versus gate_check, run_check, or find, and no exclusions or preconditions. The agent must infer that this is a broad 'what needs attention' sweep rather than a targeted query.

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