plugin

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

With no annotations, the description must disclose behavioral traits. It only says 'Get plugin info,' implying read-only behavior but not confirming side effects, permissions, or auth needs. It does not mention that an 'id' is required or what happens when the plugin doesn't exist.

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 extremely concise (one sentence) with no wasted words. However, it could benefit from more detail without sacrificing conciseness. It is front-loaded with the core action.

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 absence of an output schema and annotations, the description is insufficiently complete. It does not explain what 'plugin info' contains or how to interpret results. The required 'id' parameter is not contextualized. A minimal viable description would mention the purpose of 'id' and return type.

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 input schema has 50% coverage (only 'vault' has a description). The tool description does not add meaning beyond the schema; it does not explain the 'id' parameter's role or expected format. For a required parameter, this omission reduces clarity.

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 'Get plugin info' clearly states the action and resource but lacks specificity. It does not mention that it retrieves info for a specific plugin via an 'id' parameter, nor does it distinguish from sibling tools like 'plugins' (likely listing all plugins) or 'plugins_enabled'. This leaves ambiguity about the exact scope.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools include 'plugins' and 'plugins_enabled', but the description does not differentiate use cases. There are no prerequisites or context signals about when this tool is appropriate.

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