aedt_native_module_summary

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

With no annotations, the description is the sole source for behavioral context. It only states what is returned, omitting any side effects, security requirements, or error behavior. For a tool that likely is read-only, this is insufficient disclosure.

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 single sentence is short but lacks precision. 'Selected no-argument summaries' is ambiguous and does not clearly convey what is summarized. Conciseness is not valuable when it sacrifices clarity.

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 absence of annotations and schema descriptions, the tool's definition is critically incomplete. It fails to describe the output schema, parameter behavior, or any contextual constraints, leaving an agent without necessary information to use it correctly.

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?

The input schema has 0% description coverage, and the description does not explain the meaning or effect of the parameters (method_names, include_methods). The phrase 'selected no-argument summaries' is vague and does not clarify how parameters control output filtering.

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 'callable method names and selected no-argument summaries for an AEDT native module.' It specifies a verb (return), resource (method names and summaries), and context (AEDT native module), distinguishing it from sibling summary tools like aedt_design_summary or aedt_materials_summary.

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_native_module_call or aedt_native_module_batch_call. There is no mention of prerequisites, exclusions, or typical use cases.

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