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 disclosing behavior. It states only that this is a 'recorder tool' with no mention of side effects, writes, permissions, outputs, or any other behavioral trait.

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 short, but this is under-specification rather than efficient conciseness. A one-sentence label that merely restates the tool name does not earn credit for good structure.

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?

With no output schema, no annotations, and five sibling tools, the description needed to explain what fractal_record_agent actually does and when to invoke it. It provides neither, so the tool cannot be reliably selected or called correctly.

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 zero documented parameters, so the baseline is 4. The description adds no parameter-level detail, but with no parameters to describe, this is not a significant 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 is 'Fractal Research MCP recorder tool: fractal_record_agent', which essentially restates the tool name and labels it as a 'recorder tool' without naming a specific verb, action, or resource. It also does nothing to distinguish this tool from sibling tools like fractal_record_claim, fractal_record_source, or fractal_record_tool.

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 or when to prefer a sibling. Given multiple record_* siblings, the description provides no selection criteria, conditions, or alternatives.

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