rush_context_pack

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

With no annotations provided, the description must carry the full behavioral burden. It states a high-level operation but does not disclose side effects, cache writes, file modifications, return format, or failure behavior. The allow_cache_write parameter hints at a write effect, but the description never mentions it.

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 compact and readable, putting the core action and constraint upfront. However, it is so terse that it omits essential operational details, making it under-specified rather than efficiently concise.

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?

Given four parameters, no annotations, and no output schema, the description is not sufficient for an agent to confidently invoke the tool. It leaves usage context, parameter meanings, and behavioral consequences unaddressed.

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 explain the parameters. It only hints at the 'budget' parameter via 'strict token budget,' while 'path', 'symbol', and 'allow_cache_write' remain unexplained.

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 names a specific action ('Pack') and a distinct resource ('graph-pruned context outline') with a clear constraint ('strict token budget'). It communicates more than the tool name alone, though the term 'graph-pruned' is somewhat jargon-heavy and the exact meaning of 'pack' is left implicit.

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 is given for when to use this tool versus the many context-related siblings such as rush_token_outline or rush_context_retrieve. The intended use is only implied by the verb 'pack' and the token-budget phrase.

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