pull_context

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It only states the action without mentioning side effects, rate limits, or whether the tool is read-only (likely but unstated).

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 sentence, achieving brevity. However, it is overly terse and omits useful information about parameters and usage, making it less helpful despite its conciseness.

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 0% schema description coverage and no parameter explanations, the description is incomplete. The presence of an output schema reduces the need to describe return values, but the tool still requires more contextual detail about inputs and behavior.

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?

Parameter schema coverage is 0%, and the description does not explain the 'task' or 'limit' parameters. The default value for limit is given in the schema, but the description adds no semantic meaning beyond the schema itself.

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 states 'Return a compact context bundle for a task', which is a specific verb and resource, clearly indicating the tool's function. However, it lacks detail on what a 'context bundle' includes, making differentiation from siblings like search less precise.

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 on when to use this tool versus alternatives like auto_preserve_context or search. The description does not mention prerequisites, when not to use, or suitable contexts.

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