add_navigation_link

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

No annotations are provided, so the description carries the full burden. 'Add' implies a mutation, but the description says nothing about required permissions, whether it overwrites existing links, ordering behavior, or what happens on failure.

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?

Single short sentence with no wasted words. It is front-loaded with the core action, though the parenthetical could be expanded to earn its place more fully.

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 5-parameter mutation tool with no annotations and no output schema, the description is too thin. It omits permission needs, side effects, and what the return might contain.

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 coverage is 60%, with url, title, and isExternal documented but siteUrl and navType only partially. The description's mention of Quick Launch and Top Navigation hints at navType values but does not add meaning beyond what the enum already supplies.

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 ('Add a navigation link') and names the two navigation types it targets (Quick Launch, Top Navigation). Sibling tools like add_text_webpart, add_image_webpart, and remove_navigation_link are clearly distinct from this one.

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 guidance on when to use this versus remove_navigation_link or get_navigation, and no prerequisites such as permissions or site connection requirements. The parenthetical naming of nav types is a hint about scope but not usage timing.

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