plugin_preset_count

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

No annotations are provided, so the description carries full burden. It only states the tool counts built-in presets but does not disclose behavior like return type, error handling (if plugin invalid), or whether user presets are excluded. The phrase 'built-in' implies exclusion of user presets, but this is not explicit.

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, very concise. However, it could be expanded to include parameter context without losing conciseness. The structure is front-loaded but lacks detail that would improve usability.

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?

With 3 parameters, no output schema, and no parameter descriptions, the description is incomplete. The agent has no information on return value, parameter constraints, or what plugins are accessible. The tool's complexity is moderate, but the description fails to cover key aspects for correct invocation.

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 0%, and the description adds no meaning to the three parameters (index, slot, location). The schema provides names, types, defaults, and enums, but the description does not explain what they signify or how to use them. The agent must infer from parameter names alone, which is insufficient.

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 tool returns 'Number of built-in presets for plugin.' It identifies the verb (count) and resource (presets), but does not distinguish it from sibling tools like 'plugin_set_preset' or 'plugin_next_preset'. However, no other sibling tool counts presets, so purpose is clear.

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. For example, when to use 'plugin_preset_count' vs 'plugin_set_preset' or 'plugin_param_count' is not indicated. The context signals show many plugin-related siblings, but the description does not help differentiate.

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