list_trackers

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

With no annotations, the description carries the burden of behavioral disclosure. It states the tool lists trackers and the search parameter filters by name or GitHub URL, implying a read-only operation. However, it does not disclose details like pagination, search matching behavior (partial vs exact), whether empty search returns all, or the structure of the returned list. Some key behavioral traits are left undisclosed.

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 extremely concise: a single sentence stating the main action plus a brief Args section for the search parameter. Every word earns its place, no fluff, and the key information is front-loaded. This is an example of efficient, well-structured documentation.

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 list tool with one optional parameter and an output schema, the description is reasonably complete. It covers the main action and the search semantics. However, it could mention that it returns a list of trackers (though 'list' implies this) or note that it complements get_tracker. Overall, it's adequate for the tool's simplicity.

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 input schema only declares a 'search' string with a default of '', providing no semantic description. The description compensates by explaining that search 'Search by tracker name or GitHub URL,' which adds meaningful parameter semantics. This fully clarifies the parameter's purpose, though it doesn't specify case sensitivity or matching rules.

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 clearly states the tool's purpose: 'List all print trackers with optional search.' It identifies the specific resource (print trackers) and the operation (list), distinguishing it from sibling tools like list_materials or list_projects by naming the resource. The phrase 'all' and 'optional search' further clarify scope, though it doesn't explicitly contrast with get_tracker.

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: use when you need to list trackers, optionally filtering by search. However, it provides no explicit guidance on when to choose this over similar listing tools (e.g., list_materials) or the singular get_tracker. No alternatives or exclusions are mentioned, so guidance is only implied.

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