wp_list_sidebars

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It communicates a read-only listing action and specifies the returned information ('ordered widget IDs'), which is adequate for a simple list tool. It does not add extra context like empty-sidebar behavior, but none is critical for this operation.

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, tight sentence that front-loads the action and resource. Every word adds value, and there is no redundant or filler phrasing.

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 zero-parameter read-only list operation, the description is complete: it names the resource, the qualifying scope ('classic-theme'), and the output contents ('ordered widget IDs'). No further details are necessary for an agent to invoke this 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?

This tool has zero parameters, so the baseline is 4. The description adds meaning by clarifying what the output will contain, which is the only relevant semantic context for a parameter-less tool.

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 ('List') and a specific resource ('registered classic-theme sidebars'), and it clarifies the output scope ('ordered widget IDs'). This clearly distinguishes it from siblings like wp_list_widgets, which would list widgets instead of sidebars.

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 implies when to use the tool: whenever an agent needs an inventory of registered classic-theme sidebars and their widget assignments. However, it gives no explicit guidance about alternatives or exclusions, such as saying 'use wp_list_widgets to list widgets independently.'

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