Sayfa oluştur (taslak)

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

Discloses that header/footer are auto-copied from layoutFrom and that this creates a draft. The dryRun tip reveals how the tool behaves during validation. Annotations already signal write and non-destructive, so the description adds context without contradicting them.

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?

Three sentences, front-loaded with the core action, then critical constraints and prerequisites. Every sentence earns its place; no fluff.

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?

Given the tool's complexity (nested sections, 6 params, no output schema), the description covers essential behaviors: draft creation, auto-copy, field validation, and dryRun workflow. It omits return format for non-dry-run saves, but that is a minor gap for a create operation.

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 covers 83% of parameters, and the description adds key semantic meaning: do not include layout-sourced header/footer in sections, and use dryRun to avoid saving. It also reinforces the layoutFrom default. This enriches the schema without redundant restating.

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 opens with a specific verb-object pair: 'yeni bir TASLAK sayfa oluşturur' (creates a new DRAFT page), clearly distinguishing it from update_page and delete_page. The 'TASLAK' qualifier adds precise scope.

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?

Provides explicit guidance: validate fields with list_components first, use dryRun:true to test without saving, and warns against including header/footer in sections. It does not explicitly state when to use update_page for existing pages, but the context is clear enough.

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