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

With no annotations present, the description carries the full burden and does disclose meaningful behavior: observations are returned even without a signed receipt, receipts are attached separately, and it performs no service invocation, payment, or trust verdict. It omits auth requirements and rate limits, keeping it short of a 5.

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?

Three short sentences with the primary purpose front-loaded, followed by semantics and negative guarantees. Efficient, though the middle reference to the human lookup and the HTTP route is slightly more context than an agent needs.

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 does useful work explaining that observations and optional signed receipts are returned. However, with no annotations and an undocumented method parameter, the definition is only adequate for a two-parameter evidence lookup.

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 0% and the description only hints at 'endpoint' via 'exact service endpoint'. The 'method' parameter (nullable, default null) is never explained, so the description fails to compensate for the total lack of schema documentation.

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 (look up) and resource (Atinamos Assurance evidence) scoped to an exact service endpoint, which separates it from broader siblings like lookup_evidence and get_assurance_receipt. It does not name any sibling explicitly, so the differentiation is implied rather than stated.

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 'exact service endpoint' phrasing implies this tool is the exact-match counterpart to lookup_evidence, but it never explicitly says when to use this over a sibling or what the exclusion conditions are. Usage is inferable from scope, not spelled out.

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