wp_list_menu_locations

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

With no annotations present, the description shoulders the behavioral burden. It explicitly states 'read-only,' which communicates that no mutation occurs. However, it does not describe return format, ordering, or behavior when a location has no assigned menu, though this is a minor gap for such a simple list 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, front-loaded sentence with no wasted words. It communicates the operation, the resource, the read-only safety trait, and the return content in a compact form.

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 listing tool with no output schema, the description is fully sufficient. It tells the agent exactly what the tool lists and what data it returns, so no additional context is necessary to call it 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 tool has zero parameters and 100% schema description coverage of an empty schema. No parameter explanation is needed, so the description carries no burden here; the baseline score of 4 is appropriate.

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 a specific action ('List'), a distinct resource ('theme menu locations'), and the output ('assigned menu IDs'). This clearly distinguishes it from sibling tools like wp_list_menus, which would list menu objects rather than theme location assignments.

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 this tool is for reading menu location assignments, but it does not explicitly contrast it with alternatives such as wp_list_menus or wp_assign_menu_location. The 'read-only' wording and domain-specific resource give some context, but no explicit when-to-use or when-not-to-use guidance is provided.

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