taiga_projects_fans

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the basic action. It does not mention whether this is a read-only operation, any required permissions, pagination behavior, or the structure of the returned list. This lack of detail is a significant gap for an unannotated read operation.

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 sentence that is directly front-loaded with the action and resource. It contains no filler or redundant information, achieving maximum conciseness for a simple list operation.

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 tool is simple (one parameter, no output schema), and the description covers its basic purpose. However, it lacks any context about the concept of 'fans', potential pagination, or relationship to other tools. For a low-complexity tool, this is minimally viable but not fully helpful.

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?

Schema description coverage is 100% with a single parameter 'id' described as 'Project ID'. The tool description adds the context that the list pertains to a project, but does not meaningfully extend beyond the schema. The baseline of 3 is appropriate given the high schema coverage.

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 fans of a project' uses a specific verb ('List') and resource ('fans of a project'), making the tool's function immediately clear. It distinguishes from sibling tools like taiga_projects_watchers, as 'fans' is a distinct concept, and there is no ambiguity in the action.

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 this tool compared to alternatives. The description provides no exclusions or contextual use cases, leaving the agent without criteria to choose this over similar tools like taiga_projects_watchers or taiga_projects_get.

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