List Active Archicad Instances

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

No annotations provided, so description carries full burden. Describes scanning behavior but does not explicitly state that the operation is read-only or non-destructive. Lacks details on permissions, network usage, or potential side effects, though implied safe by nature.

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?

Two sentences, 25 words. Front-loaded with purpose; second sentence adds essential context about port usage. No redundant information.

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?

Has output schema (not detailed but present), no parameters. Description adequately covers purpose and how output is used. Could mention that the list includes port numbers and possibly other fields, but sufficient for task.

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?

No parameters in schema (schema coverage 100%). Baseline is 4 per rules. Description adds no parameter info, but none needed.

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?

Clearly states the tool scans for and lists all running Archicad instances. Identifies the resource ('running Archicad instances') and the action ('scans for and lists'). Differentiates from siblings by focusing on instance discovery rather than calling tools or discovering tool definitions.

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?

Implicitly guides usage by stating the listed port is required for other commands, indicating this tool should be used first. Does not explicitly mention when not to use it or provide alternatives, but sibling tool names suggest distinct purposes.

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