Katzilla MCP

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds valuable behavioral context beyond annotations: it specifies the source ('arXiv'), terms of use, update frequency ('updates daily'), and details about the return structure ('Katzilla envelope { data, quality, citation }') including quality scores and citation metadata. This enriches the agent's understanding without contradicting 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 efficiently structured in two sentences: the first states the purpose and return fields, and the second adds source, update frequency, and return structure details. Every sentence provides essential information without redundancy, making it front-loaded and zero-waste, which is ideal for quick agent comprehension.

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 complexity (search with two parameters), rich annotations (covering read-only, non-destructive, idempotent, open-world traits), and the presence of an output schema (implied by 'Has output schema: true'), the description is complete. It covers purpose, source, update behavior, and return structure, compensating well for any gaps. With annotations and output schema handling safety and output details, no additional explanation is needed.

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%, with both parameters ('query' and 'limit') well-documented in the schema. The description does not add any parameter-specific semantics beyond what the schema provides (e.g., it doesn't explain query syntax or limit implications). Given the high schema coverage, the baseline score of 3 is appropriate, as the description adds no extra parameter details but doesn't need to compensate for gaps.

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 specific action ('Search the arXiv preprint server for scientific papers') and resource ('arXiv preprint server'), distinguishing it from siblings like 'science__pubmed' or 'science__semantic-scholar' by specifying the arXiv source. It explicitly mentions the return fields (titles, authors, abstracts, arXiv IDs) and the Katzilla envelope structure, making the purpose highly specific and differentiated.

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 clear context for usage ('Search the arXiv preprint server for scientific papers') and mentions the source and update frequency ('Source: arXiv, updates daily'), which helps set expectations. However, it does not explicitly state when to use this tool versus alternatives like 'science__crossref' or 'science__openalex', nor does it provide exclusions or prerequisites, leaving some guidance gaps.

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