taiga_epics_watchers

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It correctly implies a read-only operation via 'List', but it does not disclose details such as authentication requirements, return format, or pagination. The simple verb 'list' makes the core behavior clear, but richer context is absent.

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, efficient sentence with no unnecessary words. It front-loads the key information and avoids extraneous detail, making it highly concise for such a simple 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?

The low complexity (1 required parameter, no output schema) makes a brief description somewhat acceptable, but the lack of any mention of the return format or how watchers are represented is a gap. Without an output schema, the description could have clarified what the response contains, and it does not situate the tool relative to the many similar watchers tools.

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 has 100% coverage with the parameter 'id' described as 'Epic ID'. The description adds no additional meaning beyond the schema. Given the high schema coverage, the baseline 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 'List watchers of an epic' clearly states the action (list) and the target resource (watchers of an epic). It is specific enough to distinguish from sibling tools like taiga_epics_voters or taiga_epics_watch, as it explicitly focuses on watchers of an epic.

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 taiga_epics_voters, taiga_epics_watch, or watchers tools for other entities. There are no context cues, prerequisites, or exclusionary statements, leaving the agent to infer usage from the name alone.

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