rush_context_pack

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions a 'strict token budget' and 'graph-pruned context outline', which hints at the tool's behavior, but it does not disclose side effects, whether it writes to cache (despite the allow_cache_write parameter), what happens when the budget is exceeded, or whether the operation is read-only or mutating. The description is too terse to provide meaningful behavioral transparency.

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 single short sentence, which is concise, but it is under-specified rather than efficiently informative. It front-loads the core action but omits essential context. It earns a middle score because it is not verbose, but it does not use its brevity to deliver high-value information.

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 the tool has 4 parameters, no output schema, no annotations, and 0% schema description coverage, the description is far from complete. An agent cannot determine what inputs are required, what the output looks like, or what side effects may occur. The tool appears to be part of a large family of rush_* tools, and without more context, an agent is likely to misuse it.

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 for the four parameters, but it only mentions 'token budget' (mapping to budget) and 'context outline' (loosely mapping to path). It does not explain what 'path' refers to, what 'symbol' selects, or what 'allow_cache_write' controls. The description adds minimal meaning beyond the schema and leaves most parameters semantically opaque.

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 'Pack graph-pruned context outline under a strict token budget' names a specific verb ('pack') and resource ('context outline'), and mentions a token budget, which gives a rough sense of the operation. However, it does not explain what 'graph-pruned' means or what the output artifact is, and it does not distinguish this tool from the many sibling context-related tools like rush_context_retrieve, rush_token_outline, or rush_context_gain_stats. The purpose is clear enough at a high level but lacks the specificity needed to differentiate it from siblings.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or exclusions, and it does not reference any sibling tools. An agent would have to infer from the name and description that this is for packing context, but there is no explicit routing information.

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