Server version & changelog

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds genuine context beyond them by disclosing that responses also include runtime capabilities (PNG rendering, filesystem access), which an agent would not learn from the schema.

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 purpose, then a compact mode-by-mode breakdown. Efficient and scannable, though the parenthetical example for 'since' slightly duplicates the schema's own example.

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?

There is no output schema, but the description compensates by describing what each mode returns (version, release date, release notes, per-release history, full history, runtime capabilities). An agent has everything needed to call it correctly and interpret the result.

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 description coverage is 100%, so all four parameters are self-documenting. The description reinforces the semantics of all/since/version by mapping each to an outcome, but adds no syntax or constraint detail beyond the schema, and never mentions the 'language' enum parameter.

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?

States a specific verb and resource ('Report which version of smith-charts-mcp is running and what changed between versions') and clearly distinguishes itself from the design/chart-rendering siblings. An agent knows immediately this is a metadata/introspection tool.

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?

Enumerates every mode of invocation with the exact selection condition: no arguments for current release, 'version:' for one release's notes, 'since:' for changes after a version (with a natural-language example), and 'all:' for full history. Nothing about argument choice 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.