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

With no annotations, the description must carry the full behavioral burden. It discloses a 24-hour renewable lifetime and a signed receipt, but omits critical traits such as required authentication, side effects, and whether the tool modifies state. This is insufficient for a trust-related operation.

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 a single sentence and avoids fluff, but it packs multiple concepts ('identity surfaces, schema availability and drift') into a dense phrase that is not front-loaded with the tool's action. It is concise but not optimally structured for quick comprehension.

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 zero parameters and no output schema, the description should fully explain what the tool does and returns. Instead, it leaves the core operation ambiguous and does not describe the structure or content of the trust passport, making it inadequate for correct invocation.

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 accepts no parameters, so the empty schema is fully covered. The baseline score of 4 applies because there are no parameter semantics for the description to clarify.

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 names a specific artifact ('24-hour renewable trust passport') and enumerates the surfaces it covers, but never states the action the tool performs (issue, renew, verify) or how it differs from siblings like notarize or attest_quality. An agent cannot tell whether this is a getter or a mutator from the description alone.

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?

There is no guidance on when to invoke this tool, what prerequisites exist, or which sibling tools it should be preferred over. The description offers only a static definition, leaving the agent to infer usage from the name alone.

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