get-menu

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

No annotations are provided, so the description carries the behavioral burden; it discloses that the result is a hierarchical view of topics and relationships, implying a safe read. It says nothing about caching, freshness, size of the payload, or authentication needs, leaving meaningful gaps for a no-annotation tool.

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 the core purpose before the return-shape and usage notes. Slightly verbose in restating the 'documentation topics/organization' idea twice, but nothing is wasted.

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?

No output schema exists, so the description appropriately characterizes the return value as a hierarchical navigation structure. Combined with the stated session-start usage, this is sufficient for a zero-parameter read tool, though not exhaustively detailed.

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 of 4 applies; there are no arguments whose semantics the description would need to explain. Schema coverage is reported at 100%, reinforcing that no parameter detail is missing.

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?

States a specific verb and resource ('Get the menu/navigation structure of the FeathersJS documentation') and clarifies the output is a hierarchical topic view. It is distinguishable from siblings like get-doc or search-doc by resource, though it does not explicitly contrast itself with 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?

'Called at the start of each session to understand the organization of the content' gives explicit timing and intent for invoking the tool. There is no statement of when not to use it or which sibling to prefer for other needs, but the positive guidance is clear.

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