strale_transaction

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

With no annotations, description carries full burden and discloses return payload details (inputs, outputs, latency, price, provenance, status) and authentication behavior ('Free-tier transactions are accessible by ID without an API key'). Lacks explicit safety classification or rate limit details.

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?

Three tightly constructed sentences: action/returns, usage guidance, and auth note. Every sentence delivers distinct value with no redundancy or filler.

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?

For a single-parameter retrieval tool, description fully compensates for missing output schema by enumerating all returned fields (latency, price, provenance, status). Covers debugging, audit, and auth contexts 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 has 100% coverage with 'transaction_id' already described as 'Transaction ID returned from a strale_execute call'. Description mentions 'by transaction ID' but does not add syntax, format, or constraint details beyond the schema. Baseline 3 appropriate for high schema coverage.

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 opens with specific verb 'Retrieve' and resource 'past execution record', clearly distinguishing this lookup tool from sibling 'strale_execute' by referencing 'previous strale_execute call'.

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 states three use cases: 'inspect what a previous strale_execute call returned, debug failures, or provide an audit trail', directly naming the sibling tool and clarifying when to use this vs. the execution tool.

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