plugin_params

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

The description discloses pagination and the output format, which is helpful. However, with no annotations, it fails to mention that the operation is read-only, lacks side-effect information, and does not specify required permissions. The output format is partially given but could be more detailed.

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 brief at one sentence, but it omits critical information about parameters and usage. It is under-specified rather than efficiently concise.

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 tool has five parameters, no output schema, and many sibling tools, the description is insufficient. It does not cover parameter semantics, error conditions, or typical usage scenarios, leaving the agent with incomplete guidance.

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 description provides no explanation of the five parameters (index, slot, location, limit, offset) despite 0% schema description coverage. The agent cannot infer the meaning or correct usage of these parameters from the description alone.

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 'List parameters (paginated)' clearly indicates the action and resource, distinguishing it from sibling tools like 'plugin_get_param' (single param) and 'plugin_find_param'. However, it does not explicitly state that it lists parameters for a specific plugin, relying on the tool name 'plugin_params' for context.

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 on when to use this tool versus alternatives like 'plugin_get_param' or 'plugin_find_param'. The description does not specify use cases, prerequisites, or exclusions.

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