terminology_versions

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

Adds detail beyond annotations: clarifies that ICD-10 to ICD-11 versions are read live from bundled data while others are static metadata, and specifies that ICD-10 is frozen (V2008) and transition version is 2025-01. Annotations indicate readOnly, idempotent, openWorld, which align with description.

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?

Well-structured: first sentence states core purpose, bullet points list practical use cases, final paragraph explains filtering and data sources. No unnecessary words; all content earns its place.

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?

Fully describes what is returned (version, release date, publisher, source URL, update cadence), the number of entries (8), and the behavior of the ICD-10 to ICD-11 transition data. With output schema present, return format documentation is unnecessary. Covers all relevant context for agent invocation.

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 covers 100% of the single optional parameter with enum and description. Description reinforces that omitting returns all 8 entries and passing a value filters to one, but does not add new semantic depth beyond 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?

Clearly states the tool lists version metadata (current version, release date, publisher, etc.) for all terminologies the server queries. Distinguishes from sibling tools that focus on code lookup, search, and hierarchy navigation.

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 identifies pipeline maintainers and research use cases with concrete examples (e.g., confirming ICD-11 release before batch runs, citing versions). Notes filtering behavior but does not explicitly state when not to use.

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