obsidian_plugins

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

The description declares the tool lists plugins with their enabled/disabled state, which is a behavioral trait. Annotations already provide readOnlyHint=true, so the safety profile is clear. However, it does not disclose output format, sorting, or potential limitations like pagination.

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 sentence that is concise and front-loaded. Every word adds value with no 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?

The description provides the core purpose but lacks details about output structure or behavior given the lack of an output schema. It is adequate for a simple listing tool but could be more complete.

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 description coverage is 100% with each parameter having a clear description (filter by type, format as enum, versions boolean). The tool description adds no extra meaning beyond the schema; baseline 3 is appropriate.

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 verb 'List' and the resource 'installed plugins' with the added detail of 'enabled/disabled state'. It distinguishes the tool from sibling tools like obsidian_plugin_disable or obsidian_plugin_info, which are for different actions.

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 its use for listing plugins but does not explicitly provide context on when to use this tool versus alternatives (e.g., obsidian_plugin_info for details on a single plugin). There is no mention of prerequisites or exclusions.

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