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

With no annotations provided, the description carries the full burden and discloses key behaviors: without a key it confirms existence/registration timing, with a key it proves ownership, and it never processes file contents. It also transparently explains conditional COA upgrade behavior, including that it should not be offered on unsuccessful verification.

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 longer than a one-liner but each sentence earns its place: it covers format, two verification modes, file-processing exclusion, and COA follow-up instructions. It is structured as a single paragraph with logical flow, though the format is repeated from the schema, creating minor redundancy.

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?

Given the tool's complexity (two modes, conditional output, COA workflow) and lack of output schema, the description covers almost all necessary context. It explains behavior and next-step actions, but does not describe the general response structure beyond the COA fields. This is a minor gap, as the tool's core output (existence and registration date) is implied.

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%, providing baseline 3. The description adds semantic depth by explaining the functional difference between providing or omitting the ownership_key: 'Without a key: confirms whether the record exists and when it was registered. With a key: additionally proves ownership of the record.' This goes beyond the schema's format-only descriptions.

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 primary action: 'Verify a VerixID registration record using a Record ID, optionally with an Ownership Key.' It specifies the resource (VerixID registration record) and the exact input required, distinguishing this tool from potential file-processing alternatives by explicitly stating only Record IDs and keys are handled.

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 explicit when-to-use guidance: 'Only call this when the user has explicitly provided a Record ID' and includes format validation. It also provides a clear exclusion: 'Never ask the user to upload or paste the original file — VerixID never processes file contents.' This effectively directs the agent on when to invoke the tool versus alternatives.

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