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

Annotations declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), and the description adds substantial context beyond them: the downstream effects (updates the listing, marks stale directories needs_update, opens PRs only when entry text changed) and the no-op behavior when nothing changed. It does not describe return format or error cases, but the mutation semantics are unusually well disclosed.

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?

Front-loaded with the core action, then effects, then the automatic-sync caveat and prerequisite. The parenthetical detailing directory-type-specific behavior is dense but earnable, though it is the longest single clause and slightly taxes readability.

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?

With no output schema, the description compensates by stating what happens on change and that it reports when nothing changed. Combined with prerequisites and side-effect detail, an agent has what it needs, though explicit guidance on the response payload is absent.

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?

Schema coverage is 100% and the single parameter is fully documented in-schema, including accepted formats and the pointer to list_servers, so the baseline is 3. The description's reference to "a server's GitHub repo" only loosely contextualizes the parameter and adds no syntax beyond the 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?

Opens with a specific verb and resource ("Re-read a server's GitHub repo right now") and enumerates exactly what it pulls: latest release/tag, package version, README, description, topics. This is clearly distinct from siblings like check_listings, update_listing, and get_server, which read or modify rather than pull-from-source.

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?

Explicitly states when to reach for it ("use this to sync now, for example right after a release") and gives the implicit when-not by noting paid plans sync automatically (Pro hourly, Starter daily). It also states the prerequisite: "Needs a launched server or a paid plan." Nothing is left to inference.

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