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

Beyond restating 'retrieve translated text', the description discloses nothing behavioral: no mention of what happens when a description is unavailable (that logic lives only in the replaceByRelated schema field), no response shape, no per-record batch behavior. With no output schema and a bare readOnlyHint=false/openWorldHint=true annotation pair, the description should carry more of this burden than it does.

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 purpose is front-loaded, but the second sentence is a keyword-stuffed keyword list that repeats the same phrases ('patent specification translation', 'description translation', 'translated full text') several times without adding information. It should be a single routing sentence instead of an SEO-style trigger dump.

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?

For a four-parameter retrieval tool with no output schema and zero required fields, the definition explains what is fetched and in which languages but omits essentials: that at least one of patentId/patentNumber must be supplied, how multiple IDs are returned, and what a missing-translation response looks like. Adequate, not complete.

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's mention of Chinese, English, and Japanese loosely echoes the 'lang' parameter, but adds no syntax, defaulting, batching, or priority guidance beyond what the schema already states for patentId, patentNumber, and replaceByRelated.

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 opening sentence states a specific verb and resource: 'Retrieve translated patent description (specification) text from Nexscope.' An agent knows what the tool returns. It falls short of 5 because it never distinguishes this from the untranslated sibling nexscope_patent_description_data, or from nexscope_patent_claims_translation / nexscope_patent_title_abstract_translation, leaving sibling selection ambiguous.

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 trigger-phrase list ('Triggered when users request patent specification translation…') implies the usage context and mentions the patent-ID/publikationsnummer input scenario. But it is a keyword dump rather than routing logic: there is no when-not condition and no explicit pointer to the untranslated or claims-translation alternatives.

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