uniprot_get_keyword

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

Annotations already provide readOnly and openWorld hints. Description adds detail on return structure (name, definition, category, synonyms, GO cross-refs, hierarchy), which is useful beyond 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?

Two sentences, front-loaded with purpose and examples. Efficient but could optionally list response_format options for completeness.

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 no output schema provided, description adequately lists return fields. Parameters covered for key one. Missing error handling or limits, but adequate for a simple fetch tool.

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, description must compensate. For keyword_id, it provides examples and purpose. For response_format, only default 'markdown' is implied but no allowed values or explanation of alternatives. Partial coverage.

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?

Description clearly states verb 'Fetch' and resource 'UniProt keyword by ID' with concrete examples (KW-0007, KW-0539). Distinguishes from sibling search_keywords which searches, not fetches by 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?

Implies usage when you have a specific keyword ID. Provides examples but does not explicitly state when to use alternatives like search_keywords. Still clear enough.

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