Discover Archicad API Tools

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

No annotations provided, so description carries full burden. It describes semantic search but does not disclose if it is read-only, any rate limits, or potential side effects. However, since it is a discovery tool, the behavior is reasonably inferred as safe querying.

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?

Three sentences: first states purpose, second gives query guidance, third connects to sibling tool. No extraneous words. Front-loaded with key 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?

Given the tool's simplicity (one parameter, likely straightforward output), the description is complete. It explains what it does, how to use the parameter, and its role in the tool ecosystem. Output schema is present but not described, which is acceptable.

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?

Only one parameter (query) with 0% schema coverage. Description adds significant meaning by advising on query style: 'detailed, descriptive queries' and providing example queries. This compensates for the lack of schema documentation.

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?

Description clearly states 'Performs a semantic search over all available Archicad commands to find the most relevant tools for a task'. It identifies the specific verb (semantic search) and resource (Archicad commands), and distinguishes from siblings: archicad_call_tool is for execution, discovery_list_active_archicads lists active instances.

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?

Explicitly says to use this before archicad_call_tool to find the correct tool name. Provides query tips (use detailed, action-oriented queries) with examples. Does not explicitly state when not to use, but context implies it is for discovery when tool name is unknown.

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