fcp_menu_list

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds non-obvious value by disclosing what the result contains — per-item enabled state and keyboard shortcuts — which tells the agent it can pre-check availability before acting.

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?

A single front-loaded sentence with no filler; verb and object come first. It is efficient but leaves no room for the routing hint that would make it more useful.

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?

One optional parameter, no output schema, and the description covers the return shape (enabled state, shortcuts) that the schema cannot. Only the relationship to fcp_menu_click is missing, which is a minor gap for a low-complexity read 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% and the path parameter is fully explained there (omit for menu bar, ["File"] for a menu, ["File","Share"] for a submenu). The description adds nothing about the path argument, 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 (list) and resource (Final Cut Pro menu items) and names the payload fields (enabled state, keyboard shortcuts). It does not distinguish itself from the obvious sibling fcp_menu_click, so an agent must infer the read-vs-act split.

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?

No when-to-use guidance, no mention of fcp_menu_click as the alternative for invoking what is listed, and no note on whether a UI snapshot must exist first. The agent gets only implied usage from the verb 'List'.

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