list_addons

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

With no annotations, the description carries the full burden. It discloses the tool lists addons with versions and status, indicating a read operation. There are no behavioral traits like permissions or side effects to mention, and the description adequately covers the behavior.

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 a single, clear sentence with no extraneous words. It efficiently conveys the purpose and expected output (versions and status).

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?

Given no output schema, the description provides sufficient detail for a simple listing tool: it names the resource and the fields (versions, status). It doesn't specify the exact format or additional fields, but it is complete enough for an agent to understand what the tool does.

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 schema coverage is 100%. The description adds no parameter information because none is needed. Per guidelines, the baseline is 4 for zero parameters, and no additional description is required.

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 the tool lists all installed addons/plugins, including versions and status. The verb 'List' and resource 'addons/plugins' are specific, and this tool uniquely handles listing addons among siblings like install_addon, uninstall_addon, and configure_addon.

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 implies the tool is used when you need an overview of installed addons. It does not explicitly state when not to use it or alternatives, but the context of sibling tools (install, uninstall, update) makes it clear this is for listing only, not for management.

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