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

With no annotations provided, the description carries the burden and does disclose a non-obvious behavioral trait: entries with available=false are introduction-only and cannot be executed. It also states that summaries and suitability are returned and that empty keyword triggers browsing, though it never explicitly says the tool is read-only or how results are paged.

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 content is dense and front-loaded, leading with purpose before caveats. The bilingual duplication roughly doubles the length, which is a real cost, but each clause still carries meaning.

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?

An output schema exists, so return values need no explanation, and the description still flags the important available=false executability caveat. For a simple three-parameter listing tool this is close to sufficient; only explicit read-only and pagination framing are missing.

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 description coverage is 100%, so the baseline is 3. The description adds one piece of meaning beyond the schema by explaining that an empty keyword browses pages, but limit/offset behavior is left entirely to the schema.

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 gives a specific verb and resource ('Discover available bioinformatics plotting modules by purpose or data features'), which is clearly distinct from sibling tools like draw_plot or get_module_schema. It stops short of explicitly naming the siblings an agent should choose between.

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?

It provides an implied usage hint that an empty keyword browses all pages and that searchable terms are purposes or data features, but it never states when an agent should call this instead of get_module_schema or draw_plot. The selection logic is left largely to inference.

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