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

No annotations, so the description must carry the burden; it does disclose the returned fields (trustScore, tier, verifiedIdentity, minimum-score clearance) and the default threshold, which is useful. However it never states that this is a non-mutating read, says nothing about missing/invalid passport behavior, and covers no auth or rate-limit constraints.

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, front-loaded with the action and answer, with no redundant filler. Slightly compressed to the point that the return-field list reads like a schema echo.

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 no output schema, naming the returned fields is valuable, but the description omits error/edge behavior (unknown passportId, what an insufficient score returns) that an agent needs to interpret the result correctly for a trust-gating decision.

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%, so both parameters are already documented in the schema; the description only restates the default of 500 for minScore. No additional semantics (e.g., score bounds or what a floor means for the returned boolean) are added.

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 ('Check a counterparty's Trust Passport') and adds the intent ('before bidding'). It does not differentiate from close siblings like pabandi_verify_passport or pabandi_trust_resolve, which an agent could easily confuse with this one.

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?

Gives an implied usage context ('before bidding', 'evaluate who to transact with') but no explicit when-to-use versus when-not, and no mention of the sibling verification tools. Adequate but leaves routing to inference.

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