Get Paybond Principal

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

Description states one read-only GET, idempotent, no side effects (no mutations, spend reservations, escrow changes, ledger writes), and that auth/gateway failures surface as errors. Annotations already provide readOnlyHint=true and openWorldHint=false, but description adds concrete behavior beyond annotations.

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 efficient paragraph, front-loaded with purpose, then usage, exclusions, and behavior. Every sentence is meaningful with no 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 zero parameters, good annotations, and output schema presence, description covers purpose, usage, behavior, and return fields. Could mention that no credentials are passed (already configured), but overall complete.

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?

Input schema has zero parameters; baseline is 4. Description adds value by listing returned fields (tenant_id, subject, roles), though output schema exists but is not shown. No parameter details needed.

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 confirms tenant-bound service-account principal (tenant_id, subject, roles). It distinguishes from siblings like paybond_get_intent and paybond_get_a2a_agent_card.

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 says when to call early (prerequisite before Harbor escrow, Signal reads when tenant unknown) and when not needed (once tenant_id known). Also lists exclusions: not for intent detail (use paybond_get_intent) or A2A discovery (use paybond_get_a2a_agent_card).

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