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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds useful context the annotations lack — the exact returned field set and that contact data is withheld unless include_contact is set — but says nothing about ordering guarantees, pagination, or limits beyond the schema's own bound.

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, front-loaded with purpose and returned fields, with the parameter caveat and endpoint placed after. The raw endpoint string is marginal value for an agent that calls the tool rather than the HTTP API, but nothing is padded.

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 and only two optional parameters, the description carries the return-value burden well by enumerating fields and the contact-gating rule. What is missing (order of 'most recent', default recency window, pagination) is minor given the low complexity.

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 both parameters are already documented; the baseline is 3. The description reinforces include_contact's gating behavior and reveals that limit is a path segment on the endpoint, but adds no semantics the schema does not already carry.

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 — 'The most recent peer-to-peer (Hobnob) event registrations' — and enumerates the returned fields. It implicitly contrasts 'most recent' with the date-scoped sibling qgiv_list_registrations_by_date and the single-record qgiv_get_registration, but does not name any sibling explicitly.

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?

Usage is only implied: 'most recent' suggests this is for the latest activity as opposed to a date-range query, and 'Contact details only with include_contact' hints at when to flip that flag. There is no explicit when-to-use/when-not statement and no alternative tool named.

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