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

readOnlyHint=true already tells the agent this is a safe read. The description adds real context beyond annotations: the underlying Gripp endpoint (project.get) and the 250-row paging cap, plus that archived projects appear in the results. It does not say whether archived records are included by default or what happens past the last page, which matters for a paginated list.

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 short, front-loaded sentences with no filler; the resource comes first, then the payload shape, then capabilities and endpoint. The enumerated field list is a slight run-on but earns its place given there is no output schema.

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 no output schema, the field enumeration is the main way the agent learns what a project record looks like, and it is supplied. All five parameters are covered and paging is mentioned; the remaining gap is behavioral detail about archived-project visibility and pagination termination.

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% — filters, operators, order_by, direction, max_results, and first_result are all fully described in the schema, including defaults and the 250 maximum. The description duplicates the row cap but adds no syntax or semantic detail beyond the schema, so the baseline of 3 applies.

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 projects in Gripp") and enumerates the returned fields, so an agent knows exactly what comes back. Sibling tools target other resources (contacts, hours, tasks, invoices), so the name alone already differentiates it; no explicit cross-reference is given, but none is really needed.

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 statement of when to use this versus alternatives such as gripp_get_record for a single project or gripp_list_tasks for project-related tasks. The only usage-adjacent content is a capability note (filters, paging, ordering) rather than selection guidance or prerequisites.

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