get_signer

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

Without annotations, the description carries full burden. It transparently lists the output components (metadata, balance, USD price via Chainlink) and implies read-only behavior. However, it does not disclose auth requirements, rate limits, or potential errors, which would be expected for a complete disclosure.

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?

The description is a single, clear sentence with no redundant words. It front-loads the key action and outputs, making it efficient for an AI agent to parse.

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 absence of an output schema and simple parameter set, the description adequately states what the tool returns but lacks detail on the structure of 'metadata'. For a more complete picture, it could describe typical fields or format, but it meets minimum viability.

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 baseline is 3. The description adds context that signer_id is a KMS signer ID and project_id is the project ID, but the schema already provides similar descriptions. The overall tool description does not significantly enhance parameter understanding beyond what the schema offers.

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 metadata, live native-token balance, and USD-micros price for a KMS signer. It uses a specific verb ('Get') and resource ('KMS signer'), and distinguishes from sibling tools like list_signers (which lists all signers).

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 description implies usage for retrieving detailed information on a specific signer but does not explicitly mention when to use this tool versus alternatives like list_signers. No exclusions or context for when not to use it are provided.

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