get_brite_info

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

Annotations already indicate the tool is read-only and idempotent. The description adds useful behavioral context: the detail_level parameter affects output (summary omits raw_content, full includes potentially large text), and the brite_id format is specified (e.g., 'br:ko00001'). No contradictions 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, using only 5 lines including the Args block. It is front-loaded with the main purpose and immediately clarifies parameters. Every sentence adds value without 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 that the tool has an output schema (so return format is documented), the description covers the essential aspects: purpose, parameters, and behavioral notes on detail_level. For a simple retrieval tool with two parameters, this is complete and well-covered.

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 input schema has 0% description coverage, so the description must explain parameters. It does so effectively: brite_id is explained with format example, and detail_level is explained with its enum values and the trade-off between compactness and completeness. This adds significant meaning beyond 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 clearly states the verb 'Get' and the resource 'information and hierarchy content for a KEGG BRITE entry'. It distinguishes itself from sibling tools like search_brite by focusing on retrieving details for a specific BRITE ID.

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 implies usage when you have a brite_id to get its details, but it does not explicitly state when to use this tool versus alternatives like search_brite or other info tools. No exclusions or context cues are provided.

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