GetAllElements

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully discloses that only identifiers are returned (not full element data), which is behavioral context beyond annotations, but it says nothing about scoping, volume, or performance on large plans.

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 short sentences with the core purpose front-loaded and no filler prose. The trailing parenthetical '(Tapir, Element Commands)' is organizational metadata that adds little for an agent.

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?

With 0% schema description coverage, no output schema, no required params, and an enum-typed filter array plus an undocumented databases param, the description leaves key invocation details unexplained. It does not do enough for an enum-driven filter API.

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%, so the description must carry parameter meaning, but it only alludes vaguely to a 'filter parameter' (the schema's actual param is a plural 'filters' enum array) and never mentions the 'databases' parameter at all. It fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Returns the identifier of all elements on the plan'), so an agent knows it enumerates element IDs globally. However it never distinguishes itself from close siblings like archicad_list_elements, GetElementsByType, or FilterElements, leaving overlap ambiguous.

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 only guidance is 'Use the optional filter parameter for filtering,' which restates the parameter name rather than saying when to choose this tool over GetSelectedElements, FilterElements, or archicad_list_elements. No when-not conditions or alternatives are given.

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