memory.context

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

No annotations exist, so the description must disclose behavior. It conveys that the tool pre-loads relevant contextual knowledge before starting a task, which implies it is a read-heavy, non-destructive operation. However, it does not explicitly mention whether the operation is read-only or if it has side effects like caching or logging. Still, the intended behavior is well communicated.

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 concise, front-loading the core purpose in the first sentence. The use/when-not example is efficient. Small verbosity due to mixing Portuguese and English, but it remains brief.

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 moderate complexity (2 nullable params, no output schema, no annotations), the description adequately explains what the tool does and when to use it. However, it lacks details on return value (what is in the 'pacote'? format/pagination?) and whether the operation has side effects beyond the agent's context. This leaves some ambiguity for complete automation.

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 has 2 parameters (domain, project) both nullable and with defaults, and schema description coverage is 0%. The description adds a usage example with both parameters, which provides usage context beyond the schema. However, it does not describe each parameter's meaning or constraints individually. With no schema descriptions, the baseline is 3, and this example marginally meets it.

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 opens with a strong verb+resource: 'Monta um PACOTE de contexto (regras/padrões/decisões)'. It unambiguously distinguishes this tool from siblings like memory.query and memory.reflect.

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 ('vai iniciar um trabalho...') and when NOT to use, naming specific sibling alternatives (memory.query, memory.reflect). This provides clear decision logic for tool selection.

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