noetic.orient

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

With no annotations provided, the description bears the full burden of disclosing behavior. It only vaguely hints at output ('narrated state', 'delta') and says nothing about mutations, authorization, side effects, checkpoint semantics, or scope 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 noun-phrase line is short but at the expense of clarity, using a cryptic '+'-joined construction rather than an explanatory sentence. This is under-specification rather than effective conciseness.

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?

Without annotations or an output schema, the description needed to explain what the tool returns, what the parameters mean, and what side effects may occur. It leaves all of these to inference, making the definition incomplete for reliable agent 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 0%, and the description does not explain 'sessionId' at all. 'From a checkpoint' merely echoes the parameter name 'fromCheckpoint' without adding format, default behavior, or meaning, so the description fails to compensate for the low schema coverage.

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 'Narrated state + scope-projected delta from a checkpoint' gives a vague sense of the tool's output but has no verb and does not state an explicit operation. It hints at change-from-checkpoint but does not distinguish orient from siblings like noetic.diff or noetic.observe, and it relies on specialized jargon.

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 about when to use orient instead of diff, observe, focus, query, or checkpoint. No conditions, prerequisites, or alternative-routing cues are present, so an agent has no basis for tool selection.

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