read_versioning

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the payload (which sections of VERSIONING.md are returned), which is genuinely useful, but says nothing about whether the content is live or a static snapshot, its size, or whether it is mutable or cacheable. Adequate but incomplete for a zero-annotation tool.

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?

A single front-loaded sentence with no filler: resource first, then the three content areas. Every clause earns its place and nothing is repeated.

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 zero-parameter document retrieval with no output schema, the description does the essential work by enumerating the returned content so the agent knows what to expect. No output schema exists, yet the description substitutes for it reasonably well; only the lack of any sibling routing guidance keeps it from a 5.

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 takes zero parameters, so the schema contributes nothing to explain. The baseline for a no-parameter tool is 4, and there are no parameters whose meaning the description would need to disambiguate.

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 ('Return') and an exact resource ('VERSIONING.md'), then enumerates the three content areas the file covers (semver policy, deprecation lifecycle, Conventional Commits→changelog mapping). This is well beyond a tautology, but it never distinguishes itself from the closely related sibling read_changelog, which an agent could easily confuse given the 'changelog mapping' phrase.

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 content enumeration lets an agent infer that this is the right tool when it needs versioning/deprecation policy, but there is no explicit when-to-use statement and no routing guidance versus read_changelog or read_migration. Usage is implied rather than stated.

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