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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds non-obvious behavioral context the annotations do not: the public slug is re-derived and old links keep resolving via the stable id, which is exactly the kind of side-effect information a caller needs before renaming.

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, front-loading the core action before the slug/link side effect. Every clause carries information an agent would otherwise have to guess.

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 an output schema present, return values need no explanation, and the description covers the main surprising behavior (slug re-derivation, link stability). It is only slightly short on preconditions and on what the name parameter accepts, but nothing essential to invoking the tool is missing.

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 50%: 'form' is documented while 'name' only has a maxLength constraint. The description's phrase 'and its schema title' hints that the name parameter drives both the display name and schema title, but it gives no accepted formats, length limits, or uniqueness rules beyond what the schema already shows.

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?

States a specific verb+resource ('Rename a form') and further narrows scope ('and its schema title'), which cleanly separates it from the sibling rename tools for projects, workspaces, and Discord channels. An agent can identify the target resource and the exact effect without opening the schema.

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?

The operation is unambiguous, so usage is implied rather than stated. There is no explicit when-to-use vs. alternatives guidance and no mention of prerequisites such as required permissions or whether the form must be published/unpublished first.

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