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

Annotations already provide readOnlyHint=true, so the description's 'List or read' is consistent and doesn't add much there. However, it adds 'MCP-only memory' and clarifies that notes are stored in the database, which is extra context beyond the annotations. It does not contradict any annotation. The description doesn't discuss auth requirements or error behavior, but the schema's authCode description partially covers that.

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, front-loaded sentence that states the purpose efficiently with no waste. However, it is so brief that it omits essential details about parameters and return behavior. While concise, it sacrifices necessary completeness, so it doesn't earn a 5.

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?

For a tool with four parameters and no output schema, the description is inadequate. It does not explain what 'list' vs 'read' returns, how to select a file (via name, path, or handle), or any constraints (e.g., required parameters). The only parameter described (authCode) is in the schema, not the description. The 'MCP-only memory' clue is helpful but insufficient 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?

Schema description coverage is only 25% (only authCode has a description in the schema). The tool description does not explain the meaning or usage of the 'name', 'path', or 'handle' parameters at all. Since the schema fails to describe these and the description provides no compensation, an agent cannot determine how to specify the target file. 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 function: 'List or read an agent’s private file cabinet (notes stored in the database).' It specifies the resource (private file cabinet/notes) and the actions (list or read), and adds 'MCP-only memory' to distinguish it from other life_* tools like account, city, timeline, which likely have different purposes. This is specific and unambiguous.

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 no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or sibling tools. The only hint is 'MCP-only memory', which vaguely suggests usage context but does not clarify selection criteria. An agent would have to infer when to choose this over orbitx__orbitx_life_list or other file-related tools.

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