aedt_native_get_properties

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

With no annotations, the description bears full burden. It only states it gets property names, but omits behavioral details like idempotency, side effects, prerequisites, or error conditions. The read-only nature is implied but not confirmed.

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?

A single sentence is concise, but it sacrifices important details. The structure is minimal, lacking an overview or parameter section. Acceptable for a very simple tool, but here it is under-informative given the parameter count.

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?

Despite having an output schema, the description does not explain what is returned (e.g., list of names, format). With 4 parameters and no usage guidance, the description is too brief to enable correct tool selection and use among many siblings.

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 0%, meaning the description adds no explanation for the 4 parameters (target, tab, server, module_name). Developers must infer meaning from the schema alone, which is insufficient for proper tool invocation.

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 'Get AEDT native property names from a target object' clearly states the verb 'Get' and the resource 'property names', distinguishing it from siblings like aedt_native_get_property_value (which gets values). However, it could be more precise about the scope of property names returned.

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?

No guidance is provided on when to use this tool versus alternatives such as aedt_native_get_property_value or aedt_oo_get_properties. The context indicates this is for listing property names before getting values, but this is not explicit.

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