Manage Doc Tab

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description need not repeat safety profiles. The description lists destructive actions but does not add context such as replace_existing behavior or irreversibility. It aligns with annotations without adding rich behavioral detail.

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?

A single, front-loaded sentence with an em-colon list of actions. Zero redundant words or filler; it earns its place.

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?

The tool has 9 parameters and 4 distinct actions, but the schema fills in per-action requirements and output schema exists, reducing the burden on the description. The description is minimal but sufficient with structured data. However, a sentence about prerequisites like using inspect_doc_structure for tab IDs would improve completeness.

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 all 9 parameters with descriptions (100% coverage), including action-specific requirements like 'index required for create'. The description adds no extra parameter meaning beyond the schema, so baseline 3 is appropriate.

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 resource (document tabs) and lists specific actions: create, rename, delete, populate from Markdown. This distinguishes it from other doc manipulation siblings. However, 'Manage' is a generic verb rather than a specific operation, though the list compensates.

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?

No explicit when-to-use or when-not-to-use guidance, nor alternatives. The tool's purpose is implied by the resource, but there are no exclusions or comparisons to sibling tools like inspect_doc_structure or get_doc_as_markdown.

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