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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral details beyond annotations: the ordering (followed first, then archived), the presence of an 'archived' boolean and 'archived_at' field, and the inclusion of 'recalculated cost per survey'. These specifics help the agent understand the response structure and ordering without an output schema.

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 two sentences with zero waste. It front-loads the core function and returned fields, then adds filtering and ordering details. Every sentence earns its place, and the structure is easy to parse for an agent.

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 read-only list tool with one optional parameter and no output schema, the description covers the essential behavioral expectations: what fields are returned, the default ordering, and the archived flag. It does not mention pagination, but that may not be needed for this tool. Given the annotations already cover safety and the description covers the response shape, it is nearly complete. A slight gap is lack of an explicit example or error conditions, but these are minor for a list operation.

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 single parameter project_id has 100% schema description coverage, so the schema already explains its meaning and the 'default' special value. The description adds only a brief mention ('Filter by project with project_id'), which is redundant with the schema. Per the rubric, with high coverage, baseline is 3; the description does not significantly enhance parameter understanding.

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 ('trackers of the account'), and lists the included fields (configuration, status, keywords, analysts, project, recalculated cost). It clearly differentiates from sibling tools like create_tracker, update_tracker, and archive_tracker by being the listing operation. The phrase 'Start here to find a tracker id' reinforces its role as the entry point for tracker operations.

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 gives clear usage context: filter by project via project_id, and explains the ordering of results (active first, then archived). It does not explicitly name alternatives or when-not-to-use, but the tool name and verb make it obvious this is for listing, not for mutations. The 'Start here' hint implicitly tells the agent to use this before other tracker-related operations that need an ID.

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