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 value beyond that by naming the returned fields, disclosing paging behavior, and exposing the underlying route and filter syntax (GET /api/v1/animals with filters as params[<field>]).

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 compact sentences: identity and returned fields first, filterability second, paging and the underlying route last. No filler, and the most decision-relevant content is front-loaded.

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 read-only list tool with no output schema, the description covers what is returned, how results can be narrowed, and that results are paged, which is enough to call it correctly. It stops short of describing the paging envelope (e.g. next_offset) or default limit, which an agent would have to get from the schema.

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 goes further by mapping the filterable concepts (owner, exact name, species, breed) to the parameters and stating the params[<field>] convention used to pass them. That mapping is meaning the schema alone does not convey.

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 and resource ("List animals (pets)") and enumerates the fields returned (species, breed, birthday, weight, owner, notes) plus the available filters. This is unmistakably distinct from sibling tools like gingr_list_owners or gingr_list_animal_reservations, so an agent can select it without opening the schema.

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?

The description implies usage by calling the filters "optional" and noting the result is paged, so an agent can infer that filtering and paging are supported. However, it never states when to reach for this tool versus siblings (e.g. gingr_list_animal_reservations) and gives no exclusions or prerequisites, leaving usage to inference.

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