optimize_memory

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool detects leaks and suggests patterns, but it does not clarify whether suggestions are applied automatically, whether the analysis is read-only, what side effects might occur, or what the output looks like. The verb 'suggest' hints at non-destructive behavior, but 'optimize' in the name creates ambiguity.

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 sentence with no filler. It front-loads the core action 'detect memory leaks' and follows with the secondary capability 'suggest memory-efficient patterns.' Every word earns its place.

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?

There is no output schema, so the description should explain what the caller will receive, such as a list of leaks or suggested patterns. It also lacks usage context and behavior details. While the schema covers parameters, the description is too thin to fully enable correct invocation and interpretation of results.

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 description coverage is 100%: path, detectLeaks, and suggestFixes all have meaningful descriptions. The tool description adds no additional parameter meaning, but it does not need to because the schema already fully documents the parameters. This matches the baseline of 3 for full schema 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-resource pairing: 'Detect memory leaks' and 'suggest memory-efficient patterns.' It clearly identifies the tool's domain as memory optimization, which distinguishes it from sibling tools focused on performance, complexity, code smells, dead code, dependencies, hot paths, and refactoring. However, it does not explicitly state what 'optimize' means in terms of actual changes or outputs.

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?

There is no guidance about when to use this tool versus alternatives such as analyze_performance or optimize_hot_paths. No context, prerequisites, exclusions, or selection criteria are provided. The agent must infer when memory analysis is appropriate.

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