upsert_project_target_preference

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

Description discloses behavior: refreshes usedOn, merges SDK-open props, and destructive nature aligns with annotations (destructiveHint: true). No contradictions.

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: first states purpose and behavior, second gives usage guidance. No wasted 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 annotations, schema coverage, and presence of output schema, description covers essential points for an upsert tool. Usage guidelines and behavior are clear.

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%, and description reinforces key behavior for 'props' parameter. Adds context beyond schema, e.g., 'merges SDK-open target preference props by key'.

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?

Clearly states verb 'Create or update', specific resource 'low-level ProjectTargetPreference record', and distinguishes from ordinary workflows by noting it's for 'tracker SDK parity or advanced administration'.

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 guides when to use: 'Use for tracker SDK parity or advanced administration; ordinary project and issue workflows usually do not need this tool.'

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