list_angular_modules

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

With no annotations provided, the description carries the entire burden of behavioral disclosure, but it reveals nothing about what the tool returns, whether it requires a loaded project, or whether it has side effects. It is a bare phrase with no 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 extremely short, but this is under-specification rather than effective conciseness. The single sentence adds no informative value beyond the tool name, making it prematurely terse rather than appropriately sized.

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?

Even though the tool has only one parameter and no output schema, the description is inadequate for a tool in a large family of Angular inspection tools. It does not explain return semantics, usage context, or how it differs from similar list tools, leaving the agent without sufficient context.

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% for the single 'name' parameter, so the baseline is 3. The description adds no additional meaning beyond the schema's own description, but it is not required to compensate since the schema already documents the parameter.

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 'Lists NgModules' is essentially a restatement of the tool name 'list_angular_modules', adding no new information about scope, return values, or the specific resource beyond what the name already conveys. It is technically accurate but fails to provide any additional clarity.

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 offers no guidance on when to use this tool versus sibling tools like list_angular_components, list_angular_routes, or angular_module_graph. There is no mention of prerequisites such as a loaded project or how this tool fits into workflow.

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