solanaGetAssetSignatures

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Get transaction signatures' implying a read operation, but fails to disclose pagination, rate limits, or exact output format. The input schema hints at pagination via limit/page/before/after, but this is not reinforced in the description.

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 sentence that efficiently states the core function. It is front-loaded with the action 'Get'. However, it could be slightly expanded to include behavioral context without losing conciseness, hence not a 5.

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 annotations and output schema, the description is incomplete. It does not explain what a 'signature' is, how results are ordered, or how pagination works. The tool has 6 parameters and likely returns a list, but the description omits these details, leaving the agent underinformed.

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 the input schema already documents all parameters with descriptions. The description adds no additional meaning to the parameters, nor does it clarify their usage or constraints beyond what is in the schema. Baseline of 3 is appropriate.

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 transaction signatures for a specific Solana asset, using a specific verb and resource. It distinguishes itself from sibling tools like solanaGetAsset, which fetches asset details, by focusing solely on signatures.

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 offers no guidance on when to use this tool versus alternatives like solanaGetAsset or fetchTransfers. It does not mention when not to use it or provide any context on prerequisites or preferred workflows.

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