wordpress_list_menus

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

With no annotations, description only states it returns a list with locations and item counts. Lacks disclosure on side effects, authentication, rate limits, or pagination behavior.

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?

Single sentence, efficient. The [UNIFIED] prefix is a minor detractor but does not significantly harm conciseness.

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?

Given simple tool but missing parameter explanation and no output schema, the description is incomplete. Agent needs more context for the site parameter.

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 only parameter 'site' has no schema description (0% coverage), and the description does not explain it. Agent has no clue what value to provide for 'site'.

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?

Description clearly states it lists all WordPress navigation menus and returns locations and item counts. However, it does not differentiate from sibling wordpress_list_navigations, and the [UNIFIED] prefix is unclear.

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 over alternatives like wordpress_get_menu or wordpress_list_navigations. Absence of usage context.

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