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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses the authentication requirement and that start_login does not open this tool, and states it returns the request with asset verification statuses. However, it does not mention whether it is read-only, any error conditions, or response format details. It adds some value but could be more explicit about the read-only nature and potential failures.

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?

The description is extremely concise: two sentences with no filler. The purpose is front-loaded in the first sentence, and the second provides crucial access instructions. Every word earns its place, making it highly efficient.

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 getter with one parameter, the description covers the purpose, return content, and access requirements. It does not describe the response structure, but there is no output schema, so that is not required. The authentication caveat adds completeness. The only minor gap is lack of explicit error behavior or a note that it is read-only, but these are not critical for this tool's simplicity.

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 schema already provides 100% coverage for the single 'id' parameter with the description 'Verification request ID'. The description only says 'by ID', which confirms the parameter's role but adds no additional semantic detail such as format, validation, or examples. Since schema coverage is high, the baseline is 3, and the description does not exceed that.

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?

The description clearly states the verb 'Get', the resource 'verification request', and the return value 'all its asset verification statuses'. It distinguishes itself from sibling tools like list_verification_requests (which lists) and get_verification (which likely gets a different entity). The mention of 'by ID' adds specificity.

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 provides access instructions (needs a Proof account, authenticate, and warns that start_login does not open this tool), which is useful context. However, it does not explicitly state when to use this tool versus alternatives like get_verification or list_verification_requests. The use case is implied by 'by ID' but not explicitly contrasted with siblings.

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