get_latest_minor

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

The description and tool name indicate a read-only lookup, but no annotations are present, so the description must carry the burden. It does not disclose behavior for invalid major versions, whether pre-releases are included, or the exact return format. The basic operation is clear, but edge-case behavior is left unspecified.

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 two lines: a clear purpose sentence followed by an arguments block. Every word earns its place, and the most important information is front-loaded.

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?

The tool is simple with one parameter and no output schema, so the description covers the core use. However, since there is no output schema, the return type is not explicitly stated, and edge cases (e.g., major version not found) are not addressed. Still, it is largely complete for a straightforward lookup 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?

The schema only defines 'major' as a string with no description. The description compensates by specifying it as 'A PostgreSQL major version' and giving concrete examples like '16', '17', '18', which is valuable beyond the 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?

The description opens with 'Find the latest minor release in a given major branch,' which clearly states the action (find), the resource (latest minor release), and the scope (given major branch). This distinguishes it from sibling tools like get_summary or get_cves, which serve different purposes.

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 phrase 'in a given major branch' implies this tool is used when you already have a major version and need the smallest update, but it does not explicitly mention alternatives or when not to use it. Sibling tool names suggest other version-related queries, but no comparison is provided. Thus, it provides clear context but no exclusions.

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