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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by stating the default ordering ('most recently granted first by default') and describing what each returned grant contains, which the annotations do not convey.

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 that packs purpose, default ordering, and payload shape without waste. It is slightly dense and could be split for scannability, but every clause carries information.

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?

There is no output schema, so the description compensates by summarizing the return payload, and pagination/filtering are fully covered by the schema. Combined with annotations covering the safety profile, this is nearly complete; only explicit sibling routing and prerequisites are missing.

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 all six parameters (including glob semantics for name and cursor pagination) are already documented in the schema, giving a baseline of 3. The description only implicitly touches the sort default and adds no syntax or format detail beyond what the schema provides.

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?

Names a specific verb (Lists) and resource (configured models a project can use / grants), and distinguishes itself from the sibling models_list and model_providers_list by scoping to project grants. It also previews the payload (overrides, model name, provider config), so an agent can tell it apart from add/delete/edit siblings without opening schemas.

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 explicit when-to-use guidance, no exclusions, and no named alternatives (e.g., use models_list for the full catalog vs this tool for project grants). The project-scoped phrasing implies context but the agent must infer when this tool is the right choice.

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