list_projects

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

With no annotations provided, the description carries the burden of behavioral disclosure. It implies a read-only list operation and hints at return content via 'task counts and metadata'. However, it does not explicitly state side-effect-free behavior, default filtering (e.g., archived excluded), or any limits/pagination. The inclusion of 'all' is slightly ambiguous given the includeArchived parameter default.

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 focused sentence with no filler. It front-loads the primary action and resource, then appends the useful return detail. Every word contributes value.

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 tool with one optional parameter, full schema coverage, and no output schema, the description is near-sufficient. It tells the agent what will be returned (projects with task counts and metadata), and the parameter is defined in the schema. It could be slightly more complete with a note about default archived filtering, but that is already in the schema.

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%, so the includeArchived parameter is fully documented in the schema itself. The tool description does not add any semantics beyond the schema, matching the baseline of 3.

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 states a specific verb ('List') and resource ('Trackfusion projects'), and adds useful detail about the return content ('task counts and metadata'). It is clear enough to identify what the tool does, but it does not explicitly differentiate from sibling list tools like list_tasks or list_items; the resource name alone provides differentiation.

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 versus alternatives, no conditions, and no exclusions. The description merely states the action; an agent must infer that this is the right tool when needing a project overview. No sibling comparisons or context are provided.

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