nexus_context_pack

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds value by listing the bundle's composition (repo map slice, symbol outlines, related files), but it does not disclose any limitations, defaults, or how 'related files' are determined. No contradictions with annotations.

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, front-loaded phrase with a colon-separated list. Every word contributes to the meaning, with no filler or redundancy. It is concise and well-structured for quick scanning.

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 there is no output schema, the description should explain return value structure and usage context more thoroughly. It lists bundle components but lacks details on how related files are selected, what format the output takes, and any prerequisites. The brevity leaves significant gaps for an agent deciding whether and how to invoke 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 coverage is 50% (only focusFiles has a description). The description does not mention the parameters at all, so it adds no meaning beyond the schema. maxTokens lacks any description and the relationship between focusFiles and the generated bundle is unclear, requiring the agent to infer usage.

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 clearly identifies the tool as a task-focused context bundle composed of repo map slice, symbol outlines, and related files. This is a specific noun phrase that distinguishes it from sibling tools like nexus_repo_map or nexus_file_symbols, though it lacks a verb to indicate the action.

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 offers minimal guidance on when to use this tool. The phrase 'task-focused' implies it is for task context gathering, but there is no explicit comparison to alternatives or mention of when not to use it. This leaves the agent without clear decision criteria.

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