pressable_list_mu_plugins

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, but it only states 'Get a list' without mentioning pagination, account/site scoping details, or any side effects. It does not reveal that the tool uses page and per_page parameters or how results are returned, leaving significant behavioral ambiguity.

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 concise sentence that front-loads the action and resource, with no unnecessary words. While it is brief, it is structurally clear and easy to parse, though it sacrifices completeness for brevity.

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 the tool is a simple list operation with no output schema and no annotations, the description still fails to provide essential context such as pagination or how it differs from other plugin-related tools. The minimal description does not compensate for the lack of schema documentation, making it inadequate for full understanding.

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 schema has 0% description coverage, and the tool description completely ignores the 'page' and 'per_page' parameters. The description adds no meaning beyond the bare parameter names, failing to explain their purpose or format. This is the lowest score because the description neither lists nor explains the parameters.

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 clearly states the tool's action ('Get') and resource ('list of must-use (MU) plugins'), including scope ('for your account/sites'). It distinguishes from sibling tools like pressable_list_plugins (regular plugins) and pressable_get_mu_plugin (single plugin), making the purpose unambiguous.

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 no guidance on when to use this tool versus alternatives such as pressable_list_plugins or pressable_get_mu_plugin. It does not mention pagination or any specific scenarios, leaving the user to infer usage from the tool name and sibling context.

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