List OCSF versions

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds valuable behavioral context by specifying it lists 'bundled' versions and is a read-only operation. It doesn't contradict annotations and provides useful scoping beyond the title.

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 succinct, front-loaded with a clear one-liner, then uses a concise bullet list for usage, and closes with an alternative recommendation. No wasted words; every sentence 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?

For a simple no-parameter listing tool with strong annotations, the description is complete. It states what the tool does, when to use it, and points to the more appropriate sibling for the common case. No output schema is needed, and the return value (a list of versions) is implied.

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 tool has zero parameters, so the baseline is 4. The description doesn't need to explain parameters, and the empty schema is fully consistent with the tool's purpose.

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 clearly states 'List all bundled OCSF schema versions' with a specific verb and resource, and distinguishes itself from the sibling `ocsf_get_latest_version` by emphasizing 'all bundled' versions. The bullet points reinforce the exact purpose.

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 explicitly lists use cases (see available versions, choose a version, understand evolution) and provides a direct alternative: 'Typically you'll want to use `ocsf_get_latest_version` instead'. This gives clear guidance on when to use this tool vs. its sibling.

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