get-server-changelog

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

With no annotations, the description carries the behavioral disclosure burden. It explains that cached tools/list and response shapes are not refreshed on server changes, clarifies the semantics of the `unlearn` field, and states the no-PCE-connection requirement. This goes well beyond a basic changelog summary.

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 compact and front-loaded: purpose first, then usage triggers and a behavioral caveat, then the no-connection note. Every sentence earns its place with no filler or redundant restatement.

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 optional-parameter introspection tool with no output schema, the description provides enough context for selection and invocation, including the stale-cache caveat and the unlearn behavior. The return structure is not detailed, but 'changelog' combined with the `since` parameter makes it sufficiently inferable.

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 schema fully describes both parameters, so the baseline is 3. The description adds value by explaining the `unlearn` field as listing behavior changes that invalidate earlier assumptions, reinforcing the purpose of `unlearn_only` beyond the schema text.

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 opens with 'What changed in this MCP server,' giving a clear subject and intent. Among the PCE-focused sibling tools, its scope is unambiguous even though it does not explicitly name a sibling alternative.

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 provides concrete triggers: call when behavior mismatches expectations, after a mid-session update, or before relying on assumptions from earlier in a long session. It also notes that no PCE connection is required. It lacks explicit when-not-to-use guidance, but the context is strong.

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