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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description elaborates with critical side effects: it may create script assets, datasets, and a scenario, and replace=true replaces existing commands and variables. This adds meaningful behavioral detail that annotations alone do not convey, such as the scope of destruction and what gets created. It does not contradict annotations, and the description's mention of 'replace' aligns with destructiveHint.

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 three sentences, each earning its place: the first defines the action and inputs, the second summarizes side effects, and the third provides an exclusion with a clear alternative. It is front-loaded with the core purpose and uses no filler or repetition.

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 the tool's complexity (parsing multiple formats, side effects, replace semantics) and the absence of an output schema, the description is thorough: it covers what inputs are needed, what happens on success (returns action items), the meaning of replace, and the exclusion case. No critical operational detail is missing for an agent to decide whether to call it.

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 83%, leaving the projectId parameter undocumented in the schema. The description does not explicitly describe each parameter, but it explains the overall purpose of 'source', 'content', and 'replace', and it mentions that import may create assets/datasets/scenario, which gives context for scriptId and projectId. While it doesn't fully compensate for the missing projectId description, the schema covers most parameters, so a slight bonus above baseline is warranted.

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 a specific verb (import) and resource (open-source load test scripts into Loadster), enumerates the supported source formats, and explicitly contrasts with OpenAPI/Swagger and Postman, which are not supported. This clearly differentiates the tool from siblings like create_script and makes its purpose unmistakable.

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 explicit guidance on when to use this tool (for JMeter, k6, Locust files) and when not to (for OpenAPI/Swagger or Postman), even naming the alternative tool (create_script) to use instead. This goes beyond basic context and gives actionable routing.

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