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

With no annotations, the description carries the full burden but only states 'List your datasets.' It reveals no behavioral details such as pagination, rate limits, authentication requirements, or the effect of filters. The parameters hint at behaviors, but the description does not disclose them.

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 concise (four words), but for a tool with 9 parameters and many siblings, this brevity sacrifices useful information. It is front-loaded but undersized for the complexity.

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's complexity (9 parameters, pagination, filtering) and presence of many sibling tools, the description is woefully incomplete. It does not explain return values or how to use the parameters effectively. Even though an output schema exists, context is lacking.

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 100%, so the description does not need to add much. It adds nothing beyond the schema, meeting the baseline expectation. No value added, but also no harm.

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 'List your datasets' uses a clear verb and resource, making the basic purpose obvious. However, it does not differentiate from sibling tools like list_projects or list_entities, though the resource name itself provides some distinction.

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 usage guidelines are provided. There is no indication of when to use this tool versus alternatives (e.g., get_dataset for a single dataset, or search-related tools). Context about filtering or pagination is absent.

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