list_projects

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

With no annotations, the description carries the full burden. It does not disclose pagination, ordering, permissions, or any side effects (though likely none). 'Get all' is simple, but the absence of additional behavioral context leaves the agent uncertain about response shape or system limits.

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, directly front-loaded sentence with no filler or repetition. Every word adds meaning.

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 simple 0-param list tool with no output schema, the description is largely sufficient. It clearly states resource and scope. It could mention return type or hidden constraints, but the simplicity makes it near-complete.

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 tool has zero parameters, so the schema is trivially complete. The description adds no parameter info because none is needed. Baseline 4 is appropriate given the 0-param context.

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 'Get all TestRail projects' clearly states a specific action (get) on a specific resource (projects) with a scope ('all'). It strongly distinguishes from siblings like get_project (singular) and list_suites (different resource).

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?

The description implies usage: call this to retrieve all projects. However, it does not explicitly contrast with get_project or mention when to choose this over other listing tools. The guidance is inferred from the resource naming but not stated.

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