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

The description explicitly states 'Read-shaped tools only (anything that buys, sells or writes refuses)', indicating the tool is read-only. However, the annotations declare readOnlyHint=false, which contradicts this. This is a direct contradiction, so the score is 1.

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 core purpose is in the first sentence, but the description includes extra promotional and contextual text ('Orbitx's MCP server, a live seat on The Wall (hosted by them). Called through their seat; their data comes back as it is.') that is not essential for tool invocation. It is moderately concise but contains non-functional fluff.

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 has 4 parameters with 0 required, but the description does not explain their semantics or how they interact. There is no output schema, and the description does not mention return format. For a simple list/read tool, the missing parameter guidance makes it incomplete 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 schema has only 25% description coverage (only authCode is described). The tool description provides no explanation of the parameters (name, path, handle, authCode) and does not compensate for the schema's lack of detail. The agent is left without guidance on what these parameters mean or how to use them.

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 lists or reads an agent's private file cabinet (notes stored in the database), which is a specific verb+resource. It also adds the 'MCP-only memory' qualifier. It does not explicitly name sibling tools, but the purpose is 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 implies it is for read-only operations ('Read-shaped tools only') and mentions it is called through Orbitx's seat, but it does not explicitly state when to use this tool versus alternatives or when not to use it. The guidance is implied rather than explicit.

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