search_articles

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

The annotations already cover the side-effect profile (read-only, idempotent, non-destructive), so the description does not need to restate safety. However, it adds no behavioral context such as what fields are searched, how the optional instance is resolved, or what happens when max_results is exceeded; it is minimally acceptable but not enlightening.

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 short and front-loads the purpose, but the 'Args' section mostly repeats the schema's property names and defaults. It is not bloated enough to hurt, but the lower-value lines prevent a higher score.

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 simple read-only search with schema and output schema available, this is close to sufficient. Still, the description leaves important selection context implicit, notably the semantics of query and the meaning of omitting instance, so an agent gets only a partial operational picture.

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 0%, so the description must compensate, but the Args block adds only near-tautological labels: 'query: Search string' and 'max_results: Max results'. The one small addition is identifying instance as a 'YouTrack instance (optional)', yet the description still omits query syntax and how the empty/default instance is interpreted.

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 phrase 'Search Knowledge Base articles' gives a specific verb and resource and clearly distinguishes this from sibling tools like search_issues because it targets KB articles rather than issues or users. It lacks only added scope or filtering context, which would push it to a 5.

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?

No guidance is given about when to prefer this tool over sibling alternatives such as search_issues or get_article. The description implies a query-based search use case but never states exclusions or conditions, leaving tool selection to inference.

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