Get Reputation Receipt

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

Describes idempotent read with no side effects, and the return behavior when no receipt exists (returns null). Adds context beyond readOnlyHint annotation, such as tenant-scoping 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?

Single paragraph with no wasted words. Front-loads purpose, then provides alternatives, requirements, and behavior. Every sentence adds value.

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?

Covers all key aspects: purpose, scope, alternatives, permissions, behavior, and parameter constraints. Output schema exists but description sufficiently complements it.

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 has 100% coverage with descriptions and examples. Description adds extra constraint ('Must belong to the authenticated tenant; do not invent tenant identifiers') not in schema, improving semantics.

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 tool retrieves a signed Signal reputation receipt for one operator DID, including specific content (score, metrics, reason codes, signing material). It also distinguishes from sibling tools by naming them explicitly.

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?

Explicitly states when to use ('Use this when you need the signed Signal reputation receipt for one known tenant-scoped operator DID'), when not to use (e.g., for tenant-wide aggregates), and provides alternative tool names. Also specifies required API key permission.

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