link_stanza

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

There are no annotations, so the description carries the full behavioral burden. It reveals a useful non-effect ('Does not edit role files') and implies mutation via 'Add,' but it does not state idempotency, duplicate-link behavior, or permission requirements.

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 tight sentences, front-loaded with the action and followed by a valuable caveat. No filler or repetition of schema details.

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 combination of 4 parameters, no annotations, and no parameter descriptions makes this definition only minimally complete. It gives the core operation and target values, but misses prerequisites, identifier meaning, and how working_folder relates to the project.

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?

With 0% schema description coverage, the description must clarify parameters, but it only maps target to 'core or on-demand list.' working_folder, project, and stanza_id are left to inference from their names, with no format or identifier semantics provided.

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 exactly what it does: adds a stanza to a project's core or on-demand list. The verb 'add' and the resource 'stanza' are specific, and the closing caveat 'Does not edit role files' helps distinguish it from role-related sibling tools.

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?

Provides a clear use context: adding a stanza to a project's list, plus an explicit exclusion for role files. However, it does not name sibling alternatives such as install_stanza or unlink_stanza, so when-to-use vs. alternatives is only partially addressed.

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