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

readOnlyHint=true already establishes the safe-read profile, so the description is not burdened with that. It adds genuinely new behavioral context: the auth requirement and the two-step flow (authenticate, then call again), which an agent could not infer from annotations or an empty schema. Pagination/result-size behavior for this list tool is still undisclosed.

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?

Front-loaded with the purpose, then the access prerequisite, in two tight sentences with no filler; the parenthetical client hint earns its place. Slightly dense but appropriately sized for a zero-param read tool.

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 simple read-only list tool with no parameters and no output schema, the description covers purpose, scope, and the auth gate that could otherwise cause a failed call. It leaves out return shape and pagination, a minor gap given the absence of an 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?

The tool takes zero parameters and the schema is empty, so the baseline is 4 per the rubric. There is nothing for the description to clarify about parameters.

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 incoming verification requests') and adds a meaningful scope qualifier ('where the authenticated user is the subject'), which separates it from the many sibling list tools. It does not, however, explicitly contrast itself with near-neighbors like list_my_requests or list_verification_requests.

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 gives a real prerequisite and remediation path ('needs a Proof account... Authenticate this client... or sign in with start_login'), which is actionable usage guidance. It stops short of saying when to prefer this tool over list_my_requests or list_verification_requests, so routing among siblings is left to inference.

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