agda_retrieve_contexts

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

No annotations are provided, so the description carries the transparency burden. It only describes the basic retrieval action and omits important behaviors like async/job-handle semantics, timeout overrides, rewrite modes, and return format. This leaves the agent uncertain about side effects and execution behavior.

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 sentence with no filler or redundant details. It efficiently communicates the core purpose.

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?

Despite high schema coverage, there is no output schema and no annotations. The description does not mention return shape, async blocking behavior, or how contexts are presented. Given the complexity of parameters like async, rewrite, and deferAfterMs, the one-sentence description is insufficient for confident invocation.

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?

The schema descriptions cover 83% of parameters, including goals, async, timeoutMs, and includeRaw. The tool description adds little beyond the schema, mostly repeating 'several goal handles' already in the goals parameter description. It does not clarify less-documented parameters like rewrite.

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 uses a specific verb ('Retrieve') and a clear resource ('types and local contexts for several goal handles'). The phrase 'in one round trip' highlights the batch nature and distinguishes it from the singular sibling agda_retrieve_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?

There is no explicit when-to-use or alternative guidance, but 'for several goal handles in one round trip' implies it is the batch version of agda_retrieve_context. Sibling names reinforce this, but the description itself does not name alternatives or exclusions.

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