plugin_param_count

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

No annotations are provided, so the description must convey behavioral traits. It states 'Return number' implying a read-only operation, but it does not confirm the absence of side effects, required permissions, or clarify what 'automatable' means. For a read operation, this is minimally transparent, earning a low score.

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 short sentence, which is concise but lacks key details. It is not front-loaded with critical information; instead, it is overly minimal. While brevity is positive, it sacrifices necessary context, making it only moderately effective.

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 three parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain how to specify the plugin, what 'automatable' means, or what the return value looks like. The agent lacks sufficient information to use the tool correctly.

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 zero information about the three input parameters (index, slot, location). With 0% schema description coverage, the description fails to explain how these parameters identify a plugin or affect the output, leaving the agent to guess their semantics.

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 states the tool returns the number of automatable parameters, which is a clear verb and resource. However, it does not explicitly mention that it pertains to a specific plugin (implied by the tool name), and it doesn't differentiate from sibling tools like plugin_params which might list parameter details. Thus, it is clear but lacks full specificity.

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 provides no guidance on when to use this tool compared to alternatives such as plugin_params or plugin_find_param. There is no mention of prerequisites, context, or situations where this tool is preferred, leaving the agent without decision-making support.

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