MCP Hub

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

No annotations are provided, so the description carries the full disclosure burden. It mentions 'manually trigger' implying immediate execution, but fails to disclose safety concerns (running duplicate tasks, permission requirements), side effects, or what happens when the hook doesn't exist.

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 the primary purpose front-loaded. Every sentence earns its place. Minor deduction for the '[UNIFIED]' metadata prefix which adds no semantic value for the agent.

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 an execution tool with no output schema and zero schema coverage, the description is insufficient. It omits what the tool returns (success boolean? task output?), error handling behavior, and whether execution is synchronous or backgrounded.

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?

Schema description coverage is 0%, requiring the description to fully compensate. It only implicitly documents the 'hook' parameter ('by hook name'). It completely omits the 'site' parameter (critical for multisite) and the 'args' parameter (arguments passed to the hook callback), leaving users to guess their purpose and format.

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 specific action ('Manually trigger'), the resource ('cron job'), and the identification method ('by hook name'). This distinguishes it clearly from the sibling tool 'wordpress_advanced_cron_list' which only lists jobs rather than executing them.

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?

Provides concrete usage context ('Useful for testing or forcing scheduled tasks'), but lacks explicit guidance on when NOT to use it, prerequisites (e.g., needing the hook name from wordpress_advanced_cron_list first), or alternatives for scheduled vs immediate execution.

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