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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile needs no restating. The description adds genuinely new behavior: a hard result cap of 12 and that returned items are titles plus URLs, and that most content is Turkish. It stops short of describing relevance/sorting or empty-result behavior.

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?

Front-loaded with the verb, resource, and return format, and the Turkish hint follows as supporting detail. The bilingual restatement of 'search Opendart articles' is mildly redundant, but the second sentence adds example queries rather than repeating the first.

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 two-parameter search with no output schema, the definition covers what is searched, who it is for, language behavior, and the shape and size of results. Only result ordering or what an empty match list looks like is left unstated, which is minor.

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 coverage is 100%, so the baseline is 3; the description earns above that by giving concrete query examples and by explaining that 'most articles are in Turkish', which directly informs the choice of the 'language' enum parameter. The 2–80 character bound is left entirely to the schema.

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 ('Search Opendart's free technical articles and tutorials'), enumerates supported topic areas, and even declares the result shape ('up to 12 article titles and URLs'). It is immediately distinguishable from the course-oriented siblings.

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?

Gives clear usage context: keyword-based search, example queries ('spring security', 'flutter bloc'), and the important caveat that most articles are in Turkish. It does not mention when to prefer a different tool, but the siblings cover a different resource (courses), so the absence of explicit routing is a minor gap rather than a serious one.

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