link_memory_to_project

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the linking action and does not explain whether this is a write operation, whether existing links are overwritten, what prerequisites exist, or what 'resurfacing' entails.

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, front-loaded sentence with no redundant or filler content. Every word adds value, making it highly concise and well-structured.

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 with fully documented parameters, but the description omits important behavioral details (e.g., whether the memory must already exist, or side effects of the link). With no output schema or annotations, the description is not fully complete for an agent to predict consequences of invocation.

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 input schema already provides 100% coverage with basic descriptions ('Project name' and 'Memory row identifier'). The tool description adds no additional parameter semantics beyond the schema, so it neither helps nor hurts the agent's understanding.

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 identifies the action ('Link') and the objects involved ('a memory to a project'), and adds the purpose 'for operational resurfacing.' It is specific enough to distinguish from sibling memory tools, though it does not explicitly name alternatives.

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 phrase 'for operational resurfacing' implies a use case, but the description gives no explicit guidance on when to prefer this tool over related alternatives like memory_search or project_profile. No exclusions or conditions are mentioned.

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