search_cosmos_transactions

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides minimal information. It doesn't describe what kind of search results to expect, whether there are rate limits, authentication requirements, pagination behavior, or performance characteristics. 'Search' implies a query operation but lacks operational context.

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 extremely concise at just 5 words, front-loading the core purpose without any wasted words. Every word earns its place in conveying the essential function.

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 search tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what format results will be returned in, what events are searchable, typical use cases, or error conditions. Given the complexity of blockchain transaction searching and the lack of structured output documentation, more context is needed.

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 description mentions searching 'by events' which aligns with the 'events' parameter in the schema, but adds no additional semantic context beyond what the 100% schema coverage already provides. The schema descriptions adequately explain each parameter's purpose, so the description doesn't add meaningful value here.

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's purpose as searching Cosmos transactions by events, which is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'get_cosmos_transaction' or 'query_sui_transactions', which appear to be related transaction retrieval tools in the same server.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools for transaction retrieval across different blockchains (Cosmos, Solana, Sui) and different query methods, the description fails to indicate when this specific search-by-events approach is appropriate versus other transaction access methods.

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