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

Annotations already declare readOnlyHint=true, and the description adds pagination/filtering behavior. However, it claims cursor-based pagination and an isSubscribed parameter that are not present in the input schema, making the behavioral guidance misleading and unreliable.

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 compact and front-loads the core action in the first sentence. The second sentence is short but contains inaccuracies, so it does not fully earn its place; still, the overall structure is efficient.

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?

The output schema and annotations cover some context, but the mismatch between the described pagination/filter options and the actual schema leaves an agent without a valid way to invoke the promised cursor or isSubscribed behavior. The description is therefore not complete enough for reliable tool selection and invocation.

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 100%, so the baseline is 3, but the description introduces 'isSubscribed' and 'cursor' as though they were parameters while the schema only defines page, sort, and limit. It adds no clarifying semantics for sort and creates confusion about available arguments.

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: 'Returns a paginated list of all trackers.' This clearly distinguishes it from single-item tools like get_tracker and search-focused 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?

It gives clear context for when to use the tool: to list all trackers, with pagination and subscription-status filtering. It does not explicitly name alternatives or exclusions, but the purpose is clear enough that an agent can infer the basic use case.

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