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. The description merely lists updatable properties and does not disclose side effects or behavioral traits. For example, the schema reveals that changing 'weight' rescopes the target's open findings, and that 'uptimeKeyword' affects uptime checks, but the description itself does not mention these consequences. It also does not state whether the update is partial or full replacement, required permissions, or return behavior. With no annotations, this lack of information 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 one concise sentence with a clear action verb and a list of properties. It is front-loaded and contains no wasted words. However, it is almost too terse, as it omits important behavioral context that could be woven into a slightly longer description without sacrificing conciseness. It earns a 4 for being efficient and well-structured, but not a 5 because it sacrifices completeness for brevity.

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?

This is a complex mutation tool with 9 parameters, no annotations, and no output schema. The description is minimal and does not orient the agent on when to use it, what side effects to expect, or what the return value will be. Although the schema richly documents parameters, the description itself fails to provide the higher-level context needed for an agent to correctly select and invoke the tool, especially given the absence of annotations. The tool's complexity demands more than a single sentence.

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%, meaning every parameter already has a detailed description in the input schema. The tool description adds no semantic value beyond listing the property names (name, URL, type, etc.), which are already present in the schema. According to the rubric, when schema coverage is high, the baseline score is 3, and the description does not raise it by providing additional context or clarification.

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 clearly states the action ('Update a target's properties') and lists the specific properties (name, URL, type, environment, business weight, tags, uptime toggle). This is a specific verb+resource combination that distinguishes it from create/delete/get targets. However, it does not explicitly differentiate from sibling tools like update_test or update_journey, though the resource 'target' is clear. A score of 4 reflects clear purpose without explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusion criteria, or situations where another tool (e.g., create_target, delete_target, update_test) would be more appropriate. There is no context such as 'use this to modify an existing target' or 'for bulk changes, use import_targets.' The description is purely a statement of functionality without usage context.

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