apex_add_nav_item

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

Annotations show all hints false, providing no safety profile. The description discloses only the mutating action 'Add' but does not mention side effects, irreversibility, permission requirements, or behavior when duplicates exist. For a mutation tool, this is a minimal disclosure.

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?

The description is a single, clear sentence with no extraneous content. It front-loads the purpose and is efficiently concise.

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?

The tool is simple (create nav item), the schema fully specifies parameters, and an output schema is present. The description covers the core purpose, but omits prerequisites like requiring the target page to exist, though schema details compensate.

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 schema covers all 6 parameters with rich descriptions, including icon examples and defaults, so the description adds no parameter-specific value. The 100% schema coverage earns a baseline 3.

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 uses the specific verb 'Add' and identifies the resource as 'navigation menu item' with a clear purpose of linking to a page. This distinguishes it from sibling add tools like apex_add_page, apex_add_region, etc.

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 implies the tool is for adding navigation menu items, but provides no explicit guidance on when to use it versus alternatives, no exclusions, and no prerequisites. Users must infer the usage context from the name and description.

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