velixar_prepare_context

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

No annotations provided, so the description carries full burden. It discloses internal operations (multi-angle search, coverage check, temporal analysis) and mentions explicit gap declaration. However, it does not state whether the tool is read-only, what side effects exist, or any authorization requirements. Given no annotations, this is adequate but not comprehensive.

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?

Single sentence that efficiently conveys the core function and internal operations. Every phrase adds value with no redundancy or fluff.

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 7 parameters and no output schema, the description is too brief. It does not explain the return value (context package with gap declaration) or how it connects to sibling 'velixar_refine_context'. For a complex preparation tool, more detail is needed.

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 100%, so the schema already documents all parameters thoroughly (including defaults for token_budget and context_ttl). The description adds high-level purpose but no per-parameter elaboration beyond what the schema provides. Baseline 3 is appropriate.

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?

Description states specific verb 'assemble' with resources: token-budgeted context package, explicit gap declaration, and internal operations (multi-angle search, coverage check, temporal analysis). It distinguishes from siblings like 'velixar_context' by mentioning gap declaration and internal analysis, but does not explicitly contrast with 'velixar_refine_context'.

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 explicit when-to-use or when-not-to-use guidance. The description does not mention alternatives like 'velixar_context' (presumably simpler) or 'velixar_refine_context'. The agent must infer usage from the name and sibling list.

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