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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful context by calling it a deprecated compatibility tool and noting that records are private. It still does not explain pagination behavior, permission requirements, or what makes the records private.

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 efficient sentence. The deprecation warning is front-loaded, and no words are wasted.

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 tool is relatively simple and has an output schema, so return values need not be explained. However, both optional parameters are undocumented in the schema and the description, so an agent lacks guidance on filtering or limiting results. The description covers purpose and deprecation but not enough operational detail.

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?

There are two parameters, limit and domain, with 0% schema description coverage. The description does not mention either parameter or explain their meaning. With low schema coverage, the description should compensate, but it does not.

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 gives a specific verb and resource: list existing private Feature Memory records. It also flags the tool as a deprecated compatibility tool, which is useful. However, it does not explicitly distinguish this tool from nearby siblings such as compare_feature_memory or delete_feature.

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 gives intended use cases: export, review, or deletion. This implies when the tool is appropriate, but it does not name alternatives or say when not to use it. The deprecation note is a useful warning but is not usage routing.

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