Rank Tracker projects

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the set of fields returned, which is useful since there is no output schema, but it says nothing about result volume, defaults, or whether listing is paginated.

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 zero filler; the resource comes first and the returned fields are parenthetically scoped. Nothing is wasted.

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 read-only two-parameter list tool this is close to adequate, and the field enumeration substitutes for a missing output schema. However, it leaves the agent guessing about filtering/pagination behavior and the role of the tool as the source of project IDs for sibling rank_* calls.

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%, so the description must carry the burden of explaining the two parameters — yet it never mentions 'max' (default 100, cap 500) or 'search'. The listed items (domain, regions, schedule, last check) are return fields, not parameters, so they do not compensate for the 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 uses a specific verb plus resource ("List Rank Tracker projects") and enumerates the fields surfaced (domain, regions, schedule, last check), so an agent knows exactly what it returns. It does not distinguish itself from sibling tools such as rank_positions or rank_keyword_details, which operate on the projects this tool enumerates.

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?

There is no when-to-use guidance at all — nothing says this is the entry point whose project identifiers the other rank_* tools require, and no exclusions or alternatives are named. The agent must infer usage from the name alone.

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