list_versions

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

No annotations provided. Description only says it lists distinct values; no disclosure of behavioral traits like idempotency, rate limits, or side effects. Does not contradict annotations (none present).

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?

Two sentences with no wasted words. Purpose and use case are front-loaded. Extremely concise yet informative.

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 tool with one optional parameter and no output schema, the description covers purpose and parameter semantics adequately. Could mention the output format or that it returns distinct values, but not critical given the simplicity.

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 coverage is 100%, but the description adds extra meaning: explains that 'plugin' can be id, code, or name, that omitting is allowed if only one plugin exists, and references list_plugins for finding available plugins. This goes beyond the schema description.

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 it lists distinct plugin versions and host application names from crash data. It also gives use case (building filters) and implicitly distinguishes from siblings like list_plugins by specifying it's for crash data.

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?

Description mentions 'useful for building filters', implying a use context. However, it does not explicitly state when to use vs. alternatives (e.g., when to use list_plugins instead), nor does it provide when-not-to-use guidance.

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