Get Signed Portfolio Artifact

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

Annotations already declare readOnlyHint=true. Description adds 'Idempotent read with no side effects' and mentions auth requirements and error behavior ('auth, RBAC, feature, or gateway failures surface as tool errors'), going 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?

Description is concise (2 sentences), front-loaded with purpose, then usage guidelines and behavioral notes. No redundant information.

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 the simple schema (1 optional param) and presence of output schema and annotations, the description covers purpose, usage, parameter semantics, and behavioral aspects comprehensively.

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% with one optional parameter. Description clarifies that omitting score_version uses gateway default current model (1.0), adding context beyond the schema's description.

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?

Description clearly states the tool provides a portable, tenant-scoped signed Signal portfolio snapshot for offline verifier checks or partner sharing, distinguishing it from a public leaderboard. It uses specific verb 'get' and resource 'signed portfolio artifact'.

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 use (for signed portfolio snapshot) and provides three specific alternatives (paybond_get_portfolio_summary, paybond_get_reputation_receipt, paybond_get_fraud_assessment) with clear when-not-to-use conditions.

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