ecp_system_check_for_update

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

No annotations are provided, so the description carries the burden of explaining behavior. The description clearly states the action (check for update) and implies a read-only behavior (checking, not modifying). This is adequate for a simple check operation, though it doesn't disclose details like whether it modifies anything or what side effects might occur, but for a check operation, this level is sufficient.

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, concise sentence that fully explains the tool's purpose. There is no unnecessary verbiage, and it is front-loaded with the key verb and resource. It earns a top score for efficiency.

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 (no parameters, no output schema), the description is largely complete. It tells an agent what the tool does and implies its use in an update workflow. However, it could benefit from mentioning that it is a check that typically precedes the 'ecp_system_update' tool, to provide more contextual guidance. But for a zero-parameter check, the description is nearly sufficient.

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 coverage is 100% (vacuously). Since there are no parameters, the description doesn't need to provide parameter semantics. The description correctly identifies that it checks for updates without needing any input, which is clear and complete. A baseline of 4 is appropriate given the zero-parameter nature.

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 clear verb ('check') and a specific resource ('ECP/system update'), which makes the tool's purpose understandable. However, it does not distinguish it from the closely related sibling tool 'ecp_system_update', which is about performing the update rather than just checking, so some ambiguity remains.

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 implies that this tool should be used to check for updates, presumably before calling 'ecp_system_update' to actually perform the update. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or conditions for usage. The context signal of no parameters suggests it's a simple check, but the description could be more explicit about its role.

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