aedt_oo_get_property_value

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

With no annotations, the description must convey behavioral traits. It only states 'return a value', omitting whether the operation is read-only, error handling, or side effects. The name implies retrieval, but transparency is minimal.

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 sentence and concise, but it sacrifices detail. While brevity is good, it fails to add value beyond the name, resulting in an average conciseness score.

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 has 4 parameters and moderate complexity (OO vs native context), the description is insufficient. Output schema exists but parameter clarity and usage context are lacking, making the tool under-documented.

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%, and the description does not explain any parameters. The parameters (target, object_name, property_name, module_name) are left to inference, providing no help to the agent.

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 it returns a PyAEDT object-oriented property value, which indicates the verb and resource. However, it does not distinguish from sibling tools like 'aedt_oo_get_properties' (plural) or 'aedt_native_get_property_value', making the purpose clear but lacking 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?

No usage guidelines provided. The description does not specify when to use this tool over alternatives, such as native property retrieval or batch property reads. Given the many siblings, explicit guidance is missing.

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