Bir gün tatil mi, iş günü mü?

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

Annotations already mark the tool read-only, and the description adds meaningful behavior beyond that: it reports weekday, weekend/official holiday status, and business-day status, including the specific rule that half days count as business days. This gives an agent useful operational detail 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 two concise sentences, front-loading the core behavior and then adding the half-day caveat. The bilingual English sentence is slightly redundant but serves Turkish and non-Turkish agents without bloating the description.

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 single-parameter read-only tool with an output schema, the description covers the essential logic and an important edge case (half days). It does not state the source of official holidays, but the existence of an output schema and the simple scope make this a minor gap rather than a blocking omission.

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% for the single parameter, documenting the type and pattern. The description adds little beyond calling it 'verilen tarih', so it does not need to compensate; the schema already carries the format requirement.

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?

Description uses a specific verb 'söyler' and names the concrete resource: a given date's weekday, weekend/official holiday status, and business day status. It also scopes the behavior to Türkiye, and the focus on a single-date check distinguishes it from sibling resmi_tatiller, which likely lists holidays.

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 intended use is implied: provide a date to determine if it is a business day. However, there is no explicit guidance about when to choose this tool over resmi_tatiller or other siblings, and no exclusions are stated.

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