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

readOnlyHint=true already establishes this as a safe read; the description adds the 250-row page ceiling and the underlying API method (company.get), which is useful context. It does not cover auth requirements, rate limits, or total-result/ pagination behavior beyond the cap.

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 tight sentences with the action and resource front-loaded and the entity/field scope plus paging limit packed efficiently. No filler, though the attribute list is somewhat incidental to an agent's decision to call it.

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?

With 5 optional params, full schema coverage and a read-only annotation, the description covers purpose, scoping and the paging cap adequately. Only the shape of returned results goes unmentioned, which matters slightly given there is no output 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 description coverage is 100%, so the schema already documents filters, operators, ordering and paging fully. The description only echoes the filter/paging/ordering capabilities and the 250 max, adding no semantics beyond the schema — baseline 3.

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+resource ("List companies in Gripp") and clarifies the domain scope by naming what a company is here (customers, suppliers, prospects) plus the key attributes returned. It is distinguishable from siblings like gripp_list_contacts or gripp_list_projects, though it never explicitly contrasts with them.

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?

"Supports filters, paging (max 250 per call) and ordering" implies how to use it, but there is no explicit when-to-use or when-not-to-use guidance versus the many sibling list tools, and no prerequisites or exclusions are stated.

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