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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add what they cannot. It does add real value: the output is an exact form link, and there is an explicit data-handling constraint (no name/e-mail/phone in chat, KVKK consent happens on the form). It does not say what happens if the wrong 'need' value is chosen or whether the link is stable across calls.

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 sentences, trigger condition first, constraint second, with no redundant restatement of the tool name or schema. Every clause carries actionable information.

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 one-parameter, no-output-schema tool with full annotation coverage, the description supplies what an agent needs: when to fire, what is returned (a form link), and the privacy constraint. The only gap is disambiguation from siblings that also serve offer/training intents.

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 100% and the single 'need' parameter carries a fully enumerated 15-value list documented in the schema, so the baseline is 3. The description only echoes this with "for that need" and adds no guidance on how to pick among overlapping enum values like 'egitim' vs 'kurumsal-egitim' or 'diger'.

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 a concrete action ("return the exact Yazılım Koçu form link") plus the triggering needs (offer, meeting, project, training), which is far more specific than the title alone. It does not explicitly contrast itself with overlapping siblings such as quote_website or get_training_options, so an agent must infer the boundary between requesting a link and getting pricing/training details.

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?

Trigger conditions are stated clearly ("When the user wants an offer, a meeting or to start a project or training"), and a negative rule is included ("Do NOT collect personal data ... in the chat"). It stops short of naming which sibling tool to use for adjacent intents, so the when-not guidance is partial.

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