List Plugins

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by disclosing the return fields (ID, name, version, active status) and the name-prefix search behavior, which goes beyond the annotation-provided information.

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 two sentences, front-loaded with the core purpose and return value, followed by a concise usage guideline. Every word earns its place with no redundancy or filler.

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?

For a straightforward list tool with good annotations and complete schema coverage, the description is largely sufficient. It explains the return content and primary use cases, though it could optionally mention pagination or the default active-only behavior, but the schema already documents those details.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description reiterates the name_prefix concept and active status but does not add significant meaning beyond the schema. It does not compensate for any missing schema detail, but none is missing.

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 uses a specific verb and resource ('List ServiceNow platform plugins on an instance') and clearly states what is returned (plugin ID, name, version, active status). It addresses the intended use case of discovering installed/active plugins or finding one by name prefix, which distinguishes it from sibling tools that list other entity types.

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 clear usage context by stating when to use the tool: to discover installed/active plugins or find a plugin by name prefix. It does not explicitly mention when not to use it or alternatives, but the context is sufficient for an agent to select it appropriately.

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