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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the 4-level nesting limit and the {source:"wp", menuId} binding contract that explains how menus are referenced elsewhere. It stops short of describing volume, pagination, or what happens on an empty result.

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?

Three short sentences, front-loaded with what the tool returns and followed by the binding contract and the prerequisite rule. No filler; every clause carries information an agent needs.

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?

With no parameters and an output schema present, the description does not need to enumerate return fields, and it correctly spends its budget on the binding contract and the mandatory skill-doc prerequisite. Complete for a zero-arg read; only the absence of any volume/ordering note keeps it from a 5.

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 tool takes zero parameters, so the baseline is 4. The description mentions the `menu` attribute shape only as a downstream binding, not as an input, so no parameter meaning is left ambiguous.

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 names the resource (the site's navigation menus) and the returned shape (id, name, items nested to 4 levels), which cleanly separates it from create-menu, update-menu, and delete-menu siblings. It never states the verb 'list/retrieve all' explicitly, but the collection framing makes the read intent 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 supplies a concrete prerequisite (call get-skill-doc with id 'site-assets-contract' before the first call) and explains how a header/footer consumes a menu via the `menu` attribute, which implies the use case. It does not, however, state when to prefer this over, say, a specific menu fetch or how it relates to update-menu.

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