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

Annotations already declare the safety profile (not read-only, non-destructive, idempotent, closed-world), so the description need not restate it. What it does add — "privacy-filtered project metadata" — is opaque and unexplained, and it says nothing about what linkage means, what happens to existing links, or how the supplied metadata is used. Minimal value beyond the structured fields.

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 sentence with no filler is well front-loaded, but the brevity reads as under-specification rather than discipline given the tool's complexity and required parameters.

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 mutation tool with 4 required params, a nested object, an idempotency contract and no output schema, the description omits the effect of the call, the meaning of source/target ids, and how the optional metadata is applied. The agent lacks enough context to invoke it confidently.

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 description names no parameter at all, despite 7 parameters including a nested details object and an idempotency key whose correct usage is non-obvious. With only 71% schema description coverage, the description should be compensating, and it does not.

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 gives a verb and a resource ("Update hosted link context nodes"), so the action is identifiable, but "link context nodes" is never explained and the sibling "link_context_project_node" is not distinguished from it. An agent cannot tell which of the two linking tools applies without extra inference.

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?

There is no statement of when to use this tool, what preconditions exist, or which alternative (e.g. link_context_project_node, record_context_node, patch_project_graph) to prefer. The agent must guess from the name alone.

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