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

Annotations already declare readOnlyHint and idempotentHint, and the description adds useful access limitation context ('limited by subscription tier'). It does not mention edge cases like empty results, but the read-only and idempotent behavior is well covered by annotations.

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 compact and every sentence adds value: it explains the browsing model, the parameter sequence, the relation to download tools, and access constraints. There is no filler or redundancy.

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 output schema exists and the annotation covers read-only/idempotent behavior, the description provides enough context for an agent to call the tool correctly. It explains the full hierarchical navigation and the subscription limitation.

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 adds meaning beyond the schema by explaining the required traversal order: md_type → exchange → ticker → timeframe → date. It also clarifies that omitting all parameters lists market data types, which is not obvious from the schema alone.

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/browses the Convex Lake data catalog and explains the hierarchical drill-down behavior. It distinguishes this tool from file/download retrieval tools by noting that the output slug values are what download tools need.

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 gives strong usage context: start with no parameters to see market data types, then add parameters to drill down. It implies this is for discovery rather than file retrieval, but it does not explicitly name sibling tools or state 'use this instead of get_*_file'.

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