noetic.diff

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. It implies a read/compute operation but does not state whether it is read-only, whether it requires authentication, what side effects exist, or what 'scope-projected' actually means in terms of 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 description is very short and front-loaded with no wasted words. However, it is under-specified: 'scope-projected' is opaque, and the description would need more detail to be appropriately sized for a tool with three parameters and no annotations.

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 no annotations, no output schema, and minimal description coverage. It omits return format, checkpoint resolution semantics, scope behavior, and any relationship to sibling tools, leaving an agent with insufficient context to invoke it reliably.

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 0%, so the description must compensate. It loosely maps 'two checkpoints' to fromCheckpoint/toCheckpoint and 'scope' to sessionId, but it does not explain the direction of the diff, defaults, or behavior when parameters are omitted.

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 indicates the tool computes a delta (difference) between two checkpoints, which is a specific and identifiable purpose. It does not explicitly use a verb like 'compute' or 'return', and it does not distinguish itself from siblings such as noetic.checkpoint or noetic.recall, but the core action is understandable.

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 alternatives like noetic.checkpoint, noetic.recall, or noetic.locate. The phrase 'scope-projected' hints at a particular use case, but no explicit context or exclusions are provided.

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