context.need

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

With no annotations present, the description carries the full behavioral burden and does so thoroughly: allowlist intersection, fail-closed behavior, the stripe.charge restriction for research, non-execution of admitted tools, denied[] output, ledger recording, and sessionId defaulting are all disclosed.

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 dense but every sentence earns its place. The core purpose is front-loaded, followed by restrictions, post-conditions, defaults, and failure behavior, all in a compact, readable form.

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?

For a tool with no output schema, the description explains key return behavior (denied[]) and points to tools/list and context.inspect for further observation. It does not specify the full success response shape, but the essential operational context is present.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the fail-closed intersection, the specific research/stripe.charge restriction, and the denied[]/ledger behavior tied to the tools parameter.

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 verb and resource: 'Admit extra tools or a named pack into this session (allow-by-need).' It clearly distinguishes what the tool does from the siblings context.inspect and echo.ping by framing it as an admission action rather than inspection or echo.

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 clear context for when to use the tool: when extra tools or a pack need to be admitted. It also provides follow-up guidance (tools/list, context.inspect), though it does not explicitly enumerate when not to use it or systematically contrast it with alternatives.

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