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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile and user-scoped nature are covered; the phrase "accessible to the connected user" largely restates the closed-world hint. The description adds nothing about pagination, ordering, result caps, or auth requirements, leaving no extra behavioral context.

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?

A single front-loaded sentence with no padding, so it is concise. However, its brevity comes at the cost of under-specification rather than efficient density — almost nothing beyond the title is conveyed.

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?

Because an output schema exists, return values need not be described, and the read-only annotations cover the mutation risk. Still, for a two-parameter listing tool the description Omits any parameter meaning or usage context, so an agent cannot fully call it correctly without inspecting the schema.

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 0% and the description says nothing about the two parameters: 'limit' (max results) and 'query' (search filter). Both are only guessable from their names, and the description does not compensate for the coverage gap.

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 gives a specific verb+resource ("List custom tracks") and adds a scope qualifier ("accessible to the connected user"). It is clearly distinguishable from create/update/delete/get_custom_track by the plural-list verb, though it never names those siblings.

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?

No guidance on when to use this versus get_custom_track (single item) or the other custom-track tools, and no mention of prerequisites or whether results are paginated/filterable. The agent must infer usage entirely from the name.

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