get_enzyme_info

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds behavioral context beyond annotations, such as the two detail_level modes ('summary' vs 'full') and that it accepts prefixed IDs. No contradiction with 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 concise: two sentences for purpose followed by a clear bullet-like list for arguments. Every sentence adds value, and it is front-loaded with the tool's primary 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?

Given the tool's simplicity (2 parameters, one enum, output schema exists), the description is complete. It covers parameter formats, default behavior, and output levels without needing to describe return values due to the output schema.

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?

With 0% schema coverage, the description fully compensates by explaining enzyme_id (EC number formats including prefixed 'ec:') and detail_level (default 'summary', alternative 'full' for complete flat-file parse). This adds meaning beyond the schema's type and enum.

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 'Get detailed information for a KEGG enzyme (EC number).' It specifies the action (get) and resource (enzyme by EC number), and this specificity distinguishes it from siblings like get_gene_info or get_reaction_info.

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 examples of valid enzyme_id formats and explains the two detail_level options, but it does not explicitly state when to use this tool versus alternatives. Usage is implied but lacks explicit when-not or alternative guidance.

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