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

Beyond the readOnlyHint annotation, the description discloses that the call is free and never consumes lookups, and warns that demo/sample projects are flagged is_demo and must not be mistaken for customer sites. This is behaviorally useful context not present in the annotations.

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?

Three tightly written sentences: the first states the output and columns, the second clarifies project_id and tracking_type, and the third adds the demo caveat plus cost/first-call guidance. Every sentence earns its place with no filler.

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?

Given the tool has an output schema, the description does not need to restate return values. It covers output structure, project_id reuse, demo flags, cost behavior, and the recommended call order, so an agent has enough context to invoke it correctly.

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 schema has one optional limit parameter with zero description coverage, and the tool description never mentions limit. Since the description is expected to compensate for low schema coverage but does not, the parameter semantics are under-specified, though the parameter is optional and nominally self-explanatory.

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?

States a specific verb ('List') and resource ('Ranklogs projects') and enumerates the flattened output columns. It also positions the returned project_id as the value to pass to other tools, which distinguishes this foundational listing tool from sibling get_* tools.

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?

Explicitly instructs the agent to call this tool first to obtain valid project_id values before calling anything else. The additional note that it is free and never consumes lookups further clarifies when it is safe to use.

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