Overview

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds real value by disclosing the breadth of the payload (projects, folders, jobs, settings, license, alerts), telling the agent this is a heavyweight dashboard read rather than a narrow query.

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?

Front-loaded with the routing instruction 'Start here,' followed by a single dense enumeration sentence. The parenthetical field list is long but each item signals real payload content; no sentence is wasted.

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 no output schema, the description carries the burden of describing return values and does so thoroughly (project fields, counts, audit step, jobs, license, alerts). Only gap is the absence of any note on the optional filters' effect on the returned payload.

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% and all three filters (kind, store, folderId) are fully documented with enums in the schema. The description only implicitly suggests the unfiltered 'every tracked project' default and adds no syntax or interaction detail beyond the schema, so baseline 3 applies.

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?

States a concrete verb ('Lists') and enumerates the resources returned: projects with specific fields, folders, running/finished jobs, settings, license state and unread rank alerts. This clearly separates it from the many single-resource siblings like list_rank_alerts or get_project_board.

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?

'Start here' plus 'Use the ids it returns with every other tool' gives explicit entry-point guidance and explains how the output feeds the rest of the toolset. It does not name a competing sibling or state when not to use it, so it stops short of full alternatives coverage.

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