reassembly_window

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

No annotations are provided, and the description does not fully disclose behavior. It lacks information on side effects, authentication, safety, or what 'feasible and safe' means. The description is insufficient for an agent to understand the tool's full 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 brief with one sentence, but it could be more structured. It front-loads jargon and then specifies returns. No superfluous words, but clarity is sacrificed for brevity.

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, the description only partially describes the return value (is_empty and max concurrency). It does not cover error conditions, edge cases, or other potential return fields. The description is incomplete for effective use.

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 input schema has no descriptions, and the tool's description does not explain the meaning of each parameter ('largest_legitimate_object', 'memory_budget', 'concurrency'). Minimal context is provided, leaving the agent guessing.

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 gives a basic idea of the tool's purpose (computing a capacity window), but uses jargon ('two-sided reassembly-capacity window') and doesn't clearly state the action (e.g., 'compute' or 'get'). The return values are specified, providing some clarity.

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?

No guidance on when to use this tool versus its siblings. The description does not mention context, prerequisites, or alternatives.

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