Pin Context Memory

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

The description says 'store text,' which implies a non-destructive create operation, but the annotations declare destructiveHint: true. No behavioral detail (e.g., overwriting existing entries, irreversible changes) is provided to reconcile this contradiction, leaving the agent with conflicting signals.

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 filler. Every word contributes to conveying the tool's purpose and key options, making it appropriately concise.

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 simple 3-param tool, the description covers core details but fails to address the destructiveHint annotation, leaving a critical behavioral gap. Without an output schema, the description should clarify what happens on execution (e.g., overwrite behavior), which it does not. The contradiction further reduces completeness.

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 description coverage is 100%, and the description adds no meaning beyond the schema by simply echoing 'optional tags and project association.' The description aligns with the schema but does not enrich parameter understanding, meeting the baseline for high coverage.

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 uses a specific verb ('store') and resource ('text') and clearly states the purpose ('for semantic retrieval'). It distinguishes this from sibling tools like 'retrieve_context' and 'clear_context' by indicating a write operation.

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 purpose statement implies usage for saving text that should be semantically retrievable later, but there is no explicit guidance on when to use this tool versus alternatives, nor any conditions or prerequisites. The 'for semantic retrieval' clause provides only implicit context.

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