check_offline_media

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

With no annotations, the description carries the transparency burden. It discloses that the tool scans all project items and returns a list, but it does not explicitly state whether the operation is read-only, whether there are performance implications, or whether it triggers any media refresh. 'Checks' implies no mutation, but the implication is not spelled out.

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 that conveys the action, scope, and result with no filler. Every word earns its place.

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 simple, zero-parameter diagnostic tool, the description is nearly complete: it states the input scope and the return class. It stops short of giving the exact return item format, and the ambiguity with 'get_offline_media' is not resolved, but an agent can still select and invoke this tool confidently.

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?

There are zero parameters and the schema already covers everything (100% schema coverage). The baseline for zero-parameter tools is 4, and the description does not need to add parameter-level details.

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 states a specific verb ('Checks'), a resource ('all project items'), and the expected output ('a list of any that are offline'). It is clear on its own, but it does not distinguish this tool from the similarly named sibling 'get_offline_media', so it misses the top score.

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 use case is implied: call this when you need a list of offline project items. However, it gives no explicit when/when-not guidance and does not mention the seemingly equivalent sibling 'get_offline_media' or any need to refresh or relink media first.

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