Memory Recall

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

The annotations already set readOnlyHint=true and openWorldHint=false. The description adds valuable behavioral context beyond the annotations: it explicitly states the store holds methods only, never credentials or target data, which informs expectations about what the tool will return and what it deliberately excludes. No contradiction with annotations.

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 short and well-structured: it states the action, provides context, and adds a key constraint in just two sentences. Every word contributes to understanding the tool's purpose and scope, with no padding or redundancy.

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 description is complete for a simple retrieval tool with an output schema present. It covers the tool's purpose, when to use it, and a key limitation (no credentials or target data). The lack of parameter explanations is a minor gap, but since the output schema is defined, the description does not need to detail return values. Overall, it provides sufficient context for correct 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 schema has three parameters (query, limit, vuln_class) with 0% description coverage. The description mentions 'vulnerability class' but does not explicitly map it to the vuln_class parameter, nor does it explain the purpose of query or limit. Since schema coverage is 0%, the description fails to compensate by explaining parameter meanings, leaving the agent to guess.

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's function: retrieving proof-of-concept techniques from previous engagements for a given vulnerability class. It also distinguishes it from related tools by emphasizing that the store holds methods only, never credentials or target data, and positions it as a preliminary step before designing a PoC from scratch.

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 description provides a direct usage guideline: 'Check this before designing a PoC from scratch.' It also hints at scope by noting the store contains only methods, which implies using it when you need techniques without sensitive data. It does not explicitly name alternative sibling tools or contrast conditions, but the directive is clear enough for most use cases.

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