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

Annotations already declare readOnlyHint=true, so the safety profile is covered, but the description adds value by disclosing the return envelope ({ valid, page_stats, data:[...] }) even though no output schema exists, and by noting the underlying endpoint. It stops short of describing pagination behavior, default ordering, or auth requirements.

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?

Three short fragments, front-loaded with the core purpose and with zero filler language. The raw endpoint reference is only marginally useful to an MCP caller, but it costs a single short clause and can aid fallback to knowledgeowl_request.

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 zero-required-parameter list tool with full schema coverage, the description supplies purpose, return shape, and endpoint, which is nearly everything needed. Gaps are minor: default result count, sort order, and how page_stats relates to _page are not explained.

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 _page and params both documented inline, so the schema carries the parameter burden. The description only indirectly gestures at pagination via page_stats and adds no syntax or filtering detail beyond what the schema already says, making the baseline 3 appropriate.

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?

States a specific verb and resource ("List search synonyms") plus a parenthetical definition clarifying that these are terms treated as equivalent by search, which separates it conceptually from glossary terms or tags. It does not explicitly name a sibling it differs from, but the resource is distinct enough among the listed tools to be unambiguous.

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?

There is no explicit statement of when to use this versus knowledgeowl_list_glossary_terms or the generic knowledgeowl_request escape hatch. Usage is implied by the resource name and the definition of synonyms, which is enough to infer the purpose but leaves the agent to decide relevance on its own.

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