update_datahub_dataset

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

Annotations already indicate destructiveHint=true, but description adds transparency by specifying that only the description can be changed and that a required confirmation step is needed. No contradiction with annotations.

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?

Four sentences with clear front-loading of purpose. Every sentence adds value: usage context, required parameter, change scope, confirmation step, and exclusions with alternatives. No unnecessary words.

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 simple operation (update a single field) and no output schema, the description covers all necessary context: what the tool does, required parameter, change limits, and safety instruction. Annotations complement the safety profile.

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 coverage is 100%, so baseline is 3. Description adds meaning by reinforcing that the name parameter is only for identification and cannot be changed, and that description is the only updatable field. This provides context beyond the schema descriptions.

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?

Description clearly states the verb (modify/update), resource (DataHub dataset), and scope (description only). It distinguishes from sibling tools by explicitly mentioning not to use for creating or listing, with alternative tool names provided.

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?

Explicitly states when to use (modify an existing dataset's description) and when not to use (creating or listing), naming alternative tools. Also instructs to ask for user confirmation before executing.

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