deprecate_schema_field

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

Discloses that field remains but is flagged, and requires confirmation. No annotations provided, so description carries burden; lacks detail on reversibility or permissions but covers main effect.

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 sentences, front-loaded with purpose, no extraneous text. Efficient and well-structured.

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?

Covers key aspects: purpose, alternative, requirement. Missing details on output and definition_key parameter, but sufficient given tool simplicity.

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?

Description adds meaning by requiring confirmed: true and implying fieldgroup_id/field_name are needed, but does not explain definition_key or access_token. Schema coverage is 0%, so partial compensation.

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?

Describes marking a custom tenant fieldgroup field as deprecated, specifying verb and resource. Distinguishes from sibling deprecate_oob_field for OOB Adobe fields.

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 alternative (deprecate_oob_field) and requires confirmed: true to execute, providing clear usage context.

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