aedt_get_setup_properties

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

The description implies a read-only operation by stating it 'returns' data, but it does not explicitly declare it as non-destructive or clarify any side effects. With no annotations, the description carries the full burden but offers minimal behavioral context.

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 a single sentence of 12 words, making it concise. However, it lacks structure that could include context like parameter explanation or usage hints, making it barely adequate.

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 complexity of AEDT and the presence of sibling tools, the description is too brief. It does not explain the relationship to aedt_setup_summary or provide enough information for an agent to choose correctly. The output schema is not visible, but the description alone is insufficient for a 1-parameter tool in a domain with many similar operations.

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?

With 0% schema description coverage, the description should clarify the 'name' parameter, but it only mentions 'setup object' without explicitly linking it to the parameter. Users must infer that 'name' refers to the setup name, which could lead to ambiguity.

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 tool returns a setup object summary and its property dictionary, specifying the verb and resource. However, it does not differentiate from the sibling tool 'aedt_setup_summary', which likely serves a similar purpose.

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 like aedt_setup_summary or aedt_create_setup. There is no mention of prerequisites or when not to use it.

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