Get Project Versions

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

Discloses default behavior (exclude obsolete and inherited versions) and how to modify with parameters. Annotations already indicate read-only, idempotent, non-destructive. Description adds useful context beyond annotations.

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?

Five concise, well-structured sentences that are front-loaded with purpose, followed by output details, usage hints, behavior flags, and prerequisite. No fluff or redundancy.

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?

Despite no output schema, the description explains return format in detail. Covers all parameters, default behaviors, and prerequisites. Complete for a tool with 3 parameters and no output schema.

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 100% description coverage. Description adds value by explaining usage of parameter outputs (version names for issue fields) and prerequisite for project_id, going beyond schema definitions.

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 it lists all versions for a MantisBT project. It specifies the action and resource, but does not explicitly differentiate from sibling tools like 'get_project_categories' or 'list_projects', though the uniqueness is implied by the version focus.

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?

Provides explicit guidance on using returned version names for creating/updating issues, mentions prerequisite (project_id from list_projects), and explains default exclusions and how to include obsolete/inherited versions. Does not explicitly state when not to use the tool.

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