Get plugin config schema

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

Describes the GET request and return of schema, implying read-only behavior. No annotations provided, so the description carries full burden; it could explicitly state it's non-destructive or safe.

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?

Two concise sentences with front-loaded action and essential usage context. No extraneous information.

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 simple tool with one parameter and no output schema, the description answers what, when, and how. Complete and self-contained.

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 single parameter 'name' is described with examples, adding context beyond the schema type/required. Schema description coverage is 100%, but description provides useful example values.

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?

Clearly states it fetches the configuration schema for a plugin, specifies HTTP method and path, and gives example plugin names. Distinguishes from sibling tools like kong_get which fetch plugin instances.

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?

Explicitly says to use before creating/updating a plugin to learn valid config fields. While it doesn't mention alternatives, the context makes it clear this is a helper for schema exploration.

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