wpnav_execute

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains the prerequisite steps (discovery and schema retrieval) and the tool's role as an execution endpoint, which adds useful context. However, it lacks details on error handling, authentication needs, rate limits, or what happens during execution, leaving gaps for a tool that performs arbitrary operations.

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 two sentences that are front-loaded with the core purpose and followed by essential usage guidance. Every sentence earns its place by providing critical information without redundancy, making it highly efficient and well-structured.

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 complexity of executing arbitrary tools, no annotations, and no output schema, the description is partially complete. It covers prerequisites and basic usage but lacks details on execution behavior, error responses, or security implications. This leaves significant gaps for an agent to understand the full context of using this tool.

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 100%, so the schema already documents both parameters thoroughly. The description does not add any meaning beyond what the schema provides (e.g., it doesn't explain how 'arguments' should be structured or validated). With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 verb ('execute') and resource ('any WP Navigator tool by name'), making the purpose specific. It distinguishes this tool from its siblings by explaining its role as the execution endpoint after using wpnav_search_tools and wpnav_describe_tools for discovery and schema retrieval.

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 explicit guidance on when to use this tool: after discovering tools with wpnav_search_tools and getting their schemas with wpnav_describe_tools. It names specific alternatives (the sibling tools) and implies that this tool should not be used without prior discovery, offering clear context for usage.

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