agda_retrieve_goals

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

There are no annotations, so the description must disclose behavioral traits itself. It indicates a read operation ('Retrieve') but omits whether the call may block, how async/deferAfterMs affect execution, whether a loaded workspace is required, and what the returned goals/handles structure looks like.

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 words or redundant phrasing. It is concise and clear at a high level, though it sacrifices structured detail that would be useful for a complex tool.

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 absence of annotations and output schema, this one-sentence description is insufficient. It does not explain job/async semantics, prerequisites, return values, or relationship to sibling tools, leaving an agent without enough context to use the tool reliably.

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 input schema has 100% parameter coverage, with individual descriptions for workspace, async, timeoutMs, includeRaw, and deferAfterMs. The description adds no parameter-specific meaning, but the schema already carries the full burden, so a baseline score of 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?

The description uses a specific verb ('Retrieve') and identifies a precise resource ('current visible goals and opaque handles'). The phrase 'current visible' helps distinguish it from context/constraint retrieval siblings, though 'opaque handles' is not explained and no explicit contrast with agda_query_metavariables is given.

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 is provided about when to use this tool versus alternatives like agda_retrieve_contexts, agda_retrieve_constraints, or agda_query_metavariables. It simply states the action without any context, prerequisites, or exclusions.

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