memory.get

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It explains that this is a direct lookup (not a search), which implies it is idempotent, fast, and does not modify state. It is transparent about its behavior beyond what any structured field would provide.

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 extremely concise, consisting of three short but dense sentences. It front-loads the core purpose, follows with usage rules, and ends with an example. Every sentence is essential and efficient.

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?

Given the tool's simplicity (1 required parameter, no output schema, clear sibling relationships), the description is complete. It tells the agent everything needed to use the tool correctly, including prerequisites, exclusions, and a usage example. No additional context is necessary.

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 explains the meaning of the single parameter 'memory_id' by specifying its form ('exato') and providing a concrete example value. Even though the schema covers 0% of the description, the description fully documents the parameter's purpose and usage, adding significant value.

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 action ('Recupera UMA memória'), the specific resource ('memory_id exato'), and the method ('lookup direto, sem busca'). It distinguishes itself from sibling tools like 'memory.query' by emphasizing its direct, ID-based nature.

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 explicitly states when to use the tool ('já tem o memory_id') and provides a clear 'Do NOT use for' clause ('busca por tema (memory.query)'). It also gives a concrete example, making the usage guidance thorough and actionable.

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