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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds the content scope by naming the tracker fields, but it does not add behavioral details such as error handling, permissions, or rate 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 front-loaded sentence with no unnecessary wording. It immediately states the operation and then concisely inventories the included fields.

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?

This is a simple single-parameter read tool with rich annotations and an output schema, so the description does not need to explain return values. It is complete enough to identify the operation and its content scope, though it could include brief guidance on when to prefer this over related tracker or run tools.

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 the single tracker_id parameter is fully documented in the schema, including its source from list_citation_trackers or create_citation_tracker. The description adds no further meaning about the parameter beyond what the schema already provides, so the baseline of 3 is appropriate.

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 and resource: "Read one citation tracker," and lists the fields it covers. It clearly indicates retrieval of a single tracker rather than a list, but it does not explicitly distinguish itself from siblings such as list_citation_trackers or get_citation_run.

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?

Usage is implied by "Read one citation tracker," and the tracker_id schema references list_citation_trackers or create_citation_tracker as the source of the id. However, the description itself gives no explicit when-to-use guidance or comparison with alternatives like listing trackers or retrieving a run.

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