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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restatement. The description adds value by revealing that the payload contains steps, rules, and a handoff explanation and that it is meant to be read once up front. It does not indicate whether the content is static, workflow-specific, or how large it is.

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?

Two short sentences with no filler, and the content list comes before the read-once instruction. The first sentence is a bare noun phrase rather than a full clause, which makes it slightly fragmentary, but nothing is wasted.

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 no output schema, the description is the only source of information about what comes back, and it only broadly lists three content types. For a workflow-entry tool sitting beside letter and destination tools, it does not say which flow the guide governs or how it relates to those siblings, which is the main gap.

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 tool takes zero parameters and the schema is a closed empty object, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing.

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 names the contents ('Adımlar, kurallar ve devir açıklaması') rather than stating an action verb, but combined with the name get_guide it is reasonably clear this returns workflow documentation. It does not differentiate itself from any sibling (create_letter, get_options, search_destinations), leaving the agent to infer that it is the entry-point reference rather than a letter operation.

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?

'Akışa başlamadan bir kez oku' gives an explicit trigger condition and even a frequency hint (once), which is exactly the kind of when-to-use guidance agents need. It stops short of naming exclusions or alternatives, so it is clear context without full routing guidance.

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