get_attestations

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

With no annotations provided, the description carries full burden. It discloses it returns paginated records with specific fields and requires an operator key. It does not mention side effects (likely none) or rate limits, but adequately describes the general behavior.

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 two sentences, concise and front-loaded with the primary action. No redundant information, 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?

No output schema exists. The description lists some return fields but not the full structure or pagination metadata (e.g., total count). Adequate for a simple list tool, but lacks details on ordering or defaults.

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?

The schema has 0% description coverage. The description mentions pagination, implying 'page' and 'limit' are for that purpose, but does not explicitly define each parameter's meaning or constraints. Partial compensation for missing schema descriptions.

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 lists on-chain trust attestations by AgentRadar, specifying the verb 'List' and the resource 'attestations'. It distinguishes from siblings like 'get_attestation_by_tx' by focusing on paginated listing.

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 mentions 'Requires operator key' as a prerequisite, but does not provide explicit guidance on when to use this tool over alternatives like 'get_attestation_by_tx' or 'get_stats'. Usage context is implied but not directly stated.

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