create_wiki_link

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

The description adds the behavioral detail that a default session is used if session_id is not provided. However, no annotations exist, and it lacks info on side effects, authentication needs, or failure modes.

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 concise sentences, efficiently stating purpose and a behavioral note. No fluff, but could be slightly more informative without sacrificing brevity.

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?

Given 5 parameters (3 required) and no output schema or annotations, the description is insufficient. It does not explain the meaning of 'title', 'href', or 'order', nor any constraints or return values.

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 0%, yet the description adds no meaning for parameters beyond their schema titles. It only restates the default behavior of session_id, which is already in the schema.

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 clearly states the tool creates a wiki navigation link (sidebar entry), which is specific and distinguishes it from sibling tools like create_wiki_page or delete_wiki_link.

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 tool versus alternatives like create_wiki_page or other create_* tools. The description only mentions default session behavior, not exclusion criteria.

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