memory_attach

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

With no annotations, the description carries the full transparency burden. It discloses the dependency on an environment variable and the purpose (raw reads), but does not explain what 'attach' entails (e.g., process handle behavior, idempotency, cleanup). The behavioral insight is minimal but adequate for a simple setup tool.

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—one sentence containing the core action and a condition. It is front-loaded with the primary purpose. However, it omits parameter details, making it slightly too terse. Overall efficient but not covering all necessary information.

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 has one parameter, no annotations, and an output schema (though not described), the description is incomplete. It fails to discuss the parameter, return value, or setup implications (e.g., how to verify attachment). The agent is left without crucial 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 input schema has one parameter 'process_name' with 0% description coverage, and the description does not mention it at all. The description adds no meaning to the parameter, leaving the agent uninformed about its purpose, default behavior, or valid values. This is a critical gap.

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 purpose: 'Attach to the MSFS process for raw reads.' The verb 'attach' and resource 'MSFS process' are specific, and the additional condition 'Off unless MSFS_ENABLE_MEMORY=true' distinguishes it from sibling tools like memory_read that operate after attachment.

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 key usage condition ('Off unless MSFS_ENABLE_MEMORY=true'), indicating when the tool is available. It implies usage before raw memory reads, but does not explicitly state when to use this tool versus alternatives like memory_module_base or memory_read. Overall, clear context but lacks explicit exclusion guidance.

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