check_offline_media

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

With no annotations, the description carries the full burden. It discloses that the tool scans all project items and returns a list of offline ones, which implies a read-only check. However, it does not explicitly state that it makes no modifications, nor does it mention potential performance implications of scanning the entire project, leaving some transparency gaps.

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 sentence that is concise and front-loaded with the action ('Checks all project items') followed by the output. Every word earns its place with no redundancy or irrelevant information.

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 tool with no output schema, the description adequately explains the tool's purpose and return value. It lacks explicit mention of edge cases (e.g., what happens when no items are offline) and does not clarify its relationship to 'get_offline_media', but these are minor gaps in an otherwise complete description.

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 and the schema is empty, so the baseline is 4. There is nothing for the description to add about parameter semantics, and it correctly avoids inventing unnecessary 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 uses the specific verb 'checks' with the resource 'all project items' and states the output: 'a list of any that are offline (missing media)'. This clearly conveys what the tool does, but it does not differentiate from the sibling tool 'get_offline_media', which likely serves a similar function.

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 is provided on when to use this tool versus alternatives like 'get_offline_media' or 'refresh_media'. The description only states the function, leaving the agent to infer appropriate usage context.

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