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

With no annotations, the description carries the full behavioral burden. It adds useful non-obvious context by saying the data comes from a pinned historical provider contract and includes actual reader restrictions, but it does not explicitly state read-only behavior, side effects, auth requirements, or failure modes.

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 a compact, front-loaded phrase with no wasted words. Its terseness makes it somewhat cryptic, but it remains concise and does not bury the key detail.

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?

An output schema exists, so return value details are partly covered elsewhere. But for a tool with no annotations and an undocumented required input, the description omits essential usage context and parameter sourcing, leaving the definition materially incomplete.

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 single input parameter operation_key has 0% schema description coverage, and the description does not explain what an operation key is, where to obtain it, or what format it uses. The parameter name is somewhat self-explanatory, but the description does not compensate for the missing schema documentation.

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 indicates that the tool surfaces exact parameters/body from a pinned historical provider contract plus reader restrictions, which gives some sense of its output. However, it is a sentence fragment with no explicit verb or statement that it describes an operation keyed by operation_key, so the purpose is only implied.

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, when not to use it, or how it relates to siblings like find_nextesy_operations, preview_nextesy_operation, or read_nextesy_operation. The reference to a pinned historical contract provides context but not actionable selection guidance.

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