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

Beyond the readOnlyHint and openWorldHint annotations, the description adds value by stating it does not return personal/customer information and that other hours 'may be available'—aligning with the openWorldHint. This manages user expectations and clarifies the data scope.

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 compact (three sentences) yet densely informative: purpose, privacy, booking flow, and required parameters. It is front-loaded with the main function and contains no filler or redundant phrases.

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?

With only two required parameters, read-only behavior, and no output schema, the description covers all essential aspects: what is returned, what is not returned, how to proceed for booking, and input requirements. It gives the agent enough context to invoke the tool correctly and interpret results.

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?

The input schema already provides full descriptions for both parameters (usta as profile slug, tarih as date format), achieving 100% coverage. The description merely restates these details without adding new constraints, examples, or edge-case information, so the baseline of 3 applies.

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 description clearly states the tool returns busy hours for an approved master on a specified day, using a specific verb and resource. It distinguishes itself from the related booking tool (talep_olustur) and clarifies what it does not return (personal information).

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?

It explicitly directs the agent to use talep_olustur for definitive appointments, creating a clear when-to-use and when-not-to-use boundary. The context of checking availability is implied but unmistakable, and the note about approved masters sets an additional prerequisite.

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