getLatestTransactions

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

The annotations include readOnlyHint: true, so the safety profile is known, but the description adds no behavioral context beyond that. It does not mention ordering, pagination, limits, or what 'latest' means in terms of time or block, which would be useful for the agent.

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 short sentence, effectively restating the tool name. While it has no fluff, it is under-specified and doesn't earn its place by adding value, making it more an under-specification than a model of conciseness.

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 tool with no output schema, the description should explain what kind of transactions are returned, in what order, and any limits. It does none of this, so the agent is left without enough information to invoke the tool correctly in context.

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 two required parameters (authToken, chainName) with 0% description coverage. The description provides no explanation of what authToken is for or how to use it, and while chainName has a const 'somnia' in the schema, the description doesn't clarify any semantic meaning. The description fails to compensate for the low 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?

The description 'Get latest transactions' clearly states the verb (get) and resource (transactions), and the qualifier 'latest' gives some scope. However, it does not distinguish this from sibling tools like getRecentTransactions or getTransactionsForAddress, so it lacks sibling differentiation.

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?

No guidance is provided about when to use this tool versus alternatives. There are no exclusions, prerequisites, or context about what makes 'latest' different from other transaction-fetching tools, leaving the agent to guess.

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