add_rotated_bbox_annotations

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'validate, correct, and add' but does not specify what corrections are performed (e.g., convexity, ordering, rectangularity are enforced but this is partial—the polygon shape requirements are mentioned in the schema, not the description). The description does not state mutability, idempotency, rate limits, or error behavior. For an atomic write tool, this is a significant gap.

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?

The description is very short (single sentence, 6 words), which is concise but not optimally structured. It front-loads the action well but lacks any details about the atomic validation or correction logic. Two additional sentences could substantially improve clarity without adding bloat.

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 no output schema is shown (though context signals say 'has output schema: true'), and the tool is complex (three required params, nested validation in annotations array), the description is incomplete. It does not describe return values, success/error conditions, or the nature of automatic corrections. Parameter number is modest, but the behavioral complexity demands more explanation.

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 each parameter (dataset_id, image_path, annotations) already has a schema-level description. The annotations schema includes explicit value constraints (normalized vertices, category positivity). The description does not add new semantic value beyond what the schema provides—no examples, no defaults, no edge case guidance. Baseline score of 3 is 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 uses a clear verb-resource combination ('add rotated annotations') and specifies the atomic nature ('validate, correct, and add…atomically'). It distinguishes from siblings like add_bbox_annotations by explicitly including 'rotated' and the validation/correction step. However, 'Validate, correct, and add' conflates three actions; the description could be more precise about which corrections are applied.

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 description does not provide guidance on when to use this tool versus alternatives. Sibling tools include add_bbox_annotations and edit_rotated_bbox_annotation, but no explicit when/to-use or when-not-to-use information is given. The atomic validation hint is implicit but insufficient for an agent to select among sibling annotation tools.

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