wordpress_get_navigation

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

No annotations are provided, so the description must carry behavioral information. It discloses that the tool returns raw block-markup content, but does not clarify if it is read-only, what happens on invalid IDs, or any side effects. The read-only nature is implied by 'get' but not confirmed.

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 sentences that are dense with information: first states what it does, second provides purpose and example. No filler or repetition.

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 no output schema, the description explains what to expect (raw block-markup content) and why it is useful. It does not detail other possible return fields, but for the intended use case it is sufficiently complete.

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%, so the description should compensate. It mentions 'by ID' linking to navigation_id, but adds no semantic value for site or beyond what the schema already provides. The description is too brief to add meaningful parameter context.

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 it gets a single wp_navigation post by ID with its raw block-markup content. It distinguishes from sibling tools like wordpress_list_navigations (list) and wordpress_update_navigation (update) by explicitly linking the output to planning an update call.

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 says to use the returned content to plan an update_navigation call, giving a concrete example of fixing href values. This implies when to use the tool, though it does not explicitly state when not to use it or provide exclusion criteria.

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