import_properties

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

Annotations indicate write operations (readOnlyHint=false) and the description confirms 'create or update', which is consistent. However, beyond that, it lacks details on behavior like overwrite vs merge, error handling, or permissions. The description adds minimal extra context beyond the annotations.

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?

Extremely concise at one sentence plus a label, with no redundant information. Every word is necessary and the key points are front-loaded.

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 this is a write tool with nested object parameters and no output schema, the description is too minimal. It does not explain return values, field-level details, or any prerequisites for execution. More context is needed for completeness.

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%, so the schema already describes both parameters adequately. The description does not add any additional semantic meaning beyond what is in the schema, so 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?

Clearly states the action (import/update) and resource (system properties) with a specific verb+resource combination. Distinguishes from siblings by mentioning 'from a JSON object' and the ability to create or update, which is more specific than generic set operations.

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 any guidance on when to use this tool versus alternatives like set_system_property or bulk_set_properties. No context on prerequisites or preferred use cases is given.

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