discover_task

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

No annotations are provided, so the description must fully disclose behavioral traits. It only includes the word 'query,' which implies a read operation, but it does not state side effects, pagination details, rate limits, or what the response contains. The description provides essentially no behavioral transparency.

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 long, comma-separated enumeration of 38 variables followed by an example, forming a wall of text. It is not structured for quick comprehension, and much of the content redundantly duplicates the schema. This is over-specification without informative structure.

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?

With 38 parameters, no annotations, and no output schema, the description is severely incomplete. It does not explain the purpose of the 'by' parameter, the meaning of the numbered filter/order groups, or what data is returned. The tool appears complex, and the description fails to provide the needed context for an agent to use it effectively.

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 descriptions are merely GraphQL type references (e.g., 'GraphQL: DiscoverTaskBy!') and do not explain meaning. The description lists all parameter names and provides a truncated JSON example showing the structure of filter/order, which offers a little value. However, the required 'by' parameter remains unexplained, and the example is incomplete, so the description adds minimal semantic value beyond the schema.

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 opens with 'Discover Tasks · query discoverTask,' which essentially restates the tool name and does not explain what the tool actually does. The rest is a list of variable names and a truncated JSON example, adding no functional clarity. It fails to distinguish it from sibling tools like discover_tasks, task, or tasks.

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 guidance on when to use discover_task versus other task-related tools. The description does not mention alternatives, prerequisites, or typical use cases, leaving the agent with no information about appropriate invocation context.

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