check_updates

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

With no annotations, the description covers main behaviors: hash comparison, handling of sources, and reporting of unchecked inline skills. Does not explicitly state it is read-only but implies it.

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?

Two focused sentences, front-loaded with purpose, every sentence adds value, no unnecessary words.

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?

Covers drift detection mechanism and special case for inline skills, but lacks output format details (no output schema), leaving the return structure unclear.

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 optional 'skill' parameter is not explained in the description, leaving ambiguity about whether it filters or specifies which skills to check, despite 0% schema coverage.

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 clearly states the tool detects upstream drift for skills by comparing content hashes, distinguishing it from sibling tools like update_skill or delete_skill.

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?

Implies use before updating but lacks explicit when-to-use or when-not-to-use guidance relative to siblings like update_skill or propose_skill.

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