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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds critical operational context: rebinding decides future write permissions and binding to a sync source overwrites teammate values on the next sync. This explains the real consequence of a destructive update beyond what annotations provide.

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 compact sentences with no wasted words. The main update actions are front-loaded, followed immediately by the critical side effect of rebinding.

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 destructive but idempotent mutation with a fully described schema and no output schema, the description covers the core actions and the most important risk: overwriting teammate values on sync. The remaining details are covered by the schema and annotations.

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%, so the schema already defines every parameter, including the source enum and overwrite behavior. The description reinforces the key mutation but does not add parameter details beyond the schema, making the baseline score 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 states specific update actions for a smart field: rename, mark required, or rebind its source. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like create_smart_field or delete_smart_field beyond the update framing.

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?

Usage is implied by the listed actions (rename, mark required, rebind source), but the description does not state when to choose this tool over alternatives or mention any prerequisites. It gives enough to infer the use case but no explicit routing guidance.

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