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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered; the description adds the concrete return fields and the HTTP method, which the annotations do not convey and no output schema exists to supply. It says nothing about result-set size, truncation, or pagination behavior beyond what the schema implies.

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 tightly written sentences; the field list comes first and the downstream routing second. No redundant restatement of the name or annotations.

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 a read-only list tool with full schema coverage and no output schema, the description supplies the important missing piece: what each record contains and how the id is consumed downstream. It stops short of noting result ordering or how next_offset signals more pages, which would round it out.

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 limit, offset and search are fully documented in the schema with defaults and bounds. The description contributes no additional semantics (e.g., how search interacts with pagination or what ordering results come in), so baseline 3 applies.

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 ("List the menus (menu plans) in the account") and enumerates the returned fields (id, name, last-modified time). This cleanly separates it from the singular parsley_get_menu and from parsley_list_menu_items.

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?

Explicitly routes the agent: use the returned id with parsley_get_menu or when creating an event, and states the underlying GET /menus endpoint. It gives clear positive guidance but never says when listing is the wrong choice (e.g., searching vs. browsing, or versus parsley_list_menu_items).

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