ism_get

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

Annotations already declare readOnlyHint=true (safe read). Description adds: input tolerance (various formats), return fields (title, control text, etc.), failure on no match, defaults to active version, and version parameter for historical. No contradictions.

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?

Four concise sentences. Front-loaded with purpose and input format. Efficiently covers behavior, defaults, and alternatives. No wasted words.

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 output schema exists (signal indicates true) and annotations provide safety info, description adds all necessary context: input handling, output fields, failure mode, version defaults, and sibling guidance. Complete for a getter 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?

Schema has 0% description coverage, so description must compensate. It thoroughly explains identifier parameter (tolerant input, example, canonical ID). Version parameter is mentioned as optional with reference to ism_versions, but could provide more detail on format. Still largely covers key aspects.

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?

Description clearly states verb 'Get' and resource 'full record for one ISM control'. Identifies specific input ('by identifier') and gives example. Differentiates from siblings by recommending ism_search or ism_applicable when identifier is unknown.

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 use (known identifier) and when not to (unknown identifier, suggests alternatives). Mentions default behavior (active version) and optional parameter (version) with reference to ism_versions.

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