check_mcp_update

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

No annotations are provided. The description adds a key behavioral trait: 'Does not expose credentials,' which is important for the agent's safety considerations. It lacks mention of other traits like network usage, but for a read-like operation, this is good.

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 sentences, no fluff. The description is efficiently front-loaded with the core action and includes a crucial safety caveat.

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 zero parameters, no output schema, and no annotations, the description covers the purpose and a key safety aspect. It could optionally mention the nature of the return value, but overall adequate for a simple tool.

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, so baseline is 4. The description adds no parameter details, but none are needed. It adds purpose and safety beyond the empty schema.

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 checks the installed package version against npm's latest and returns update guidance, with a safety note. It is distinct from sibling tools which deal with Bilibili operations.

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 use when checking for MCP updates, but does not explicitly state when to use or when not to, nor mentions alternatives. Siblings are unrelated, so no confusion, but explicit guidance is absent.

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