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

With no annotations, the description carries the full burden and does well: it discloses the exact shape of the returned data, distinguishes 'accept' from 'refused' with sample reason codes (signature_invalid, rate_limited), and notably declares 'Never their URLs or secrets,' which prevents an agent from attempting to extract sensitive values. It does not cover ordering, pagination/volume limits, or permission requirements.

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 tight sentence front-loads the verb and resource, then packs the returned fields efficiently; the closing 'Never their URLs or secrets' lands as a clear constraint. The trailing ellipsis in the reason list ('signature_invalid, rate_limited, …') is slightly loose but signals that reasons are an open set.

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 must convey return content, and it does so compactly and specifically, including the sensitive-data exclusion. Gaps remain around result volume/ordering and what an agent should do if it actually needs a hook URL or secret, since no sibling appears to expose those.

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?

The tool takes zero parameters, so there is nothing beyond the schema to clarify and the baseline of 4 applies. The description's explanation of returned attributes is useful but belongs to behavioral disclosure rather than parameter meaning.

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 this project's hooks') with clear scope ('this project's') and then enumerates what each entry reports: verification method, retention, last-received time, and accept/refuse counters. The create/update/delete_hook siblings are self-evidently different operations, but the description never explicitly contrasts with them or with list_secrets.

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 by the word 'List' and the project scoping; there is no explicit 'use this when...' statement or exclusion pointing to another tool. For a no-parameter read of a fixed resource this is largely unambiguous, but the description does not help an agent decide between this and, say, inspecting secrets or hooks for another project.

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