Track Brief

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only says 'ONE-PARAGRAPH summary only,' which implies a read-only action but omits any detail on output format, side effects, permissions, or limitations. This is insufficient for a tool with zero annotation support.

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 short—a single sentence—but brevity here is under-specification rather than conciseness. It lacks any structured breakdown of purpose or behavior, and the one piece of information it does give ('ONE-PARAGRAPH summary only') is not meaningful without context.

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 parameter, no output schema, and no annotations, the description should still explain what the tool does and what 'which' means. It does neither, making it impossible for an agent to know what to expect or how to use it correctly, even though the tool itself is simple.

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 coverage is 0% and the description does not explain the 'which' parameter beyond referencing it in the track_detail call. It fails to clarify what values are valid, what the default 'track1' means, or how it affects the result, leaving the agent without essential semantic guidance.

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 it provides a one-paragraph summary but never defines what a 'track' is or what the summary covers. It references track_detail as the full spec, implying a relationship, but the core resource and action remain vague, offering no differentiation from siblings like qvac_index or hackathon_rules.

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?

It explicitly names track_detail as the alternative for a full spec, which is a useful pointer. However, it does not state when to choose this tool over track_detail or other siblings beyond a vague 'summary only' hint, so the decision criteria are incomplete.

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