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

With no annotations, the description carries the full burden of behavioral disclosure, yet it says nothing about side effects, return values, authentication, or whether it mutates state. The name implies 'recording' but does not explain consequences or behavior.

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 single sentence is short but utterly redundant with the tool name. Rather than being concise, it is under-specified and provides no actionable information, so it fails the 'every sentence earns its place' criterion.

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 description is completely inadequate for a tool with five sibling tools, no annotations, and no output schema. An agent has no way to know what the tool does, what input it accepts, what it returns, or when to choose it, making this definition effectively empty.

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 tool has zero defined parameters and the schema is an empty object with additionalProperties allowed, so there are no parameter semantics to explain. The description adds no parameter information, but with no parameters documented, this is not a meaningful gap. Baseline 4 for zero-parameter tools is appropriate.

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 'Fractal Research MCP recorder tool: fractal_record_tool' is a tautology that restates the tool name without specifying what is recorded, what action is performed, or how it differs from siblings like fractal_record_agent or fractal_record_claim. It gives only a generic label, not a clear verb+resource purpose.

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 on when to use this tool versus the sibling recording tools. No context, prerequisites, or exclusions are provided, leaving the agent to guess which tool fits a given task.

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