editor_get_plugin_list

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

With no annotations, the description carries the full burden. It states that the tool lists plugins and their enabled state, which is the core behavior. However, it does not disclose details such as return format, ordering, or potential side effects (though likely none). For a simple list, this is adequate but not rich.

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 concise sentence that delivers the essential information without any waste. It is well-structured and easy to parse.

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 the simplicity of the tool (zero parameters) and the lack of an output schema, the description provides enough information to understand what the tool returns. It could be slightly more explicit about the shape of the returned list (e.g., array of plugin names with boolean enabled), but the statement 'with enabled state' is reasonably sufficient.

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, and schema description coverage is 100%. The description adds meaningful context by confirming that the output includes enabled state, which is valuable for a parameterless tool. No further parameter-level explanation is needed.

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 uses a specific verb 'List' and clearly identifies the resource: 'installed editor plugins'. It also includes the notable detail that the enabled state is included, which differentiates it from other plugin-related tools in the sibling list that modify or enable/disable plugins.

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 usage as a read-only listing tool, but it does not explicitly state when to use it or contrast it with alternatives. Since it's a simple query tool, this is an acceptable though not explicit level of guidance.

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