ext_list

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

Describes exactly what the tool returns (id, name, version, enabled) and that it includes both loaded and disabled extensions. Annotations confirm readOnlyHint=true, so no contradiction. Adds context about Cockpit-only availability.

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 concise sentences: first states purpose and output, second provides context and related tool references. No wasted words.

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 tool with no parameters and no output schema, the description fully covers what the tool does, what it returns, its context (Cockpit only), and relevant sibling tools. Complete and self-contained.

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 no parameters and the schema is empty with 100% coverage. The description adds no parameter details, but none are needed. The context 'Cockpit only' adds value beyond 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 clearly states the tool lists Chrome extensions, specifying both loaded and disabled types and the fields returned (id, name, version, enabled). It also differentiates from siblings like ext_install and ext_set_enabled.

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?

Explicitly states it is for Cockpit only, and provides direct references to alternatives: 'Install with ext_install, toggle with ext_set_enabled.' This tells the agent when to use this tool versus others.

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