entity_list

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

There are no annotations, so the description carries the burden. 'List' clearly signals a read-only, non-mutating operation, and 'local repository' scopes it. However, it does not disclose what happens with an invalid repository_path, whether declaration_path must exist, or whether the scan is limited to architecture.yaml or the whole repo.

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 focused sentence with no filler. It front-loads the action and key scoping qualifiers ('DSL-declared', 'local repository') while staying compact.

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?

For a 3-parameter tool with a bare schema and no annotations, this description is too thin. It lacks parameter semantics, usage context, and differentiation from sibling entity/repository tools. The output schema covers return shape, but that does not compensate for missing guidance on how the parameters interact.

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 description coverage is 0% and the description adds little parameter-level meaning. 'Entity type' loosely maps to entity_name and 'local repository' to repository_path, but declaration_path is ignored, no formats or value expectations are given, and required vs optional status is not clarified.

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 uses a specific verb ('List') and a clear resource ('instances of a DSL-declared entity type from the local repository'). It differentiates from siblings like entity_read (singular) and entity_search by focusing on listing all instances from the local repo.

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 when-to-use or when-not-to-use guidance is provided. The description gives no hint about when to prefer entity_list over entity_search or entity_read, and does not mention preconditions such as a valid repository path or initialized repository.

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