close_discover_task

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

With no annotations, the description should disclose behavioral traits. It only states 'mutation' (already implied by the name) and gives an example. There is no mention of side effects, reversibility, required permissions, or what the response contains.

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 very short and includes a concrete example, earning its place. However, it is not front-loaded with a clear sentence about what the tool does; it reads more like a code snippet.

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 mutation tool with no annotations and no output schema, the description is too sparse. It lacks usage context, behavioral details, and any mention of return values, making it inadequate for an agent to fully understand the tool's impact.

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 describes the `input` parameter only as a GraphQL type, which is unhelpful. The description adds an example object with closeCode and discoverTaskId, giving some practical meaning. However, it does not explain valid values for closeCode or the structure of the input object beyond the example.

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 the operation 'closeDiscoverTask' and shows example variables with a discoverTaskId, making it clear this tool closes a discover task. However, it does not explain what 'closing' entails or distinguish it from sibling tools like update_discover_task_state.

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 on when to use this tool versus alternatives such as assign_discover_task or update_discover_task_state. The description does not mention any prerequisites, context, or exclusions.

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