list_components

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

No annotations and minimal description; doesn't disclose default limit behavior, q search semantics, required excel_path, or error/filtering behavior. Not contradictory, but very little behavioral detail.

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?

Single concise sentence with no redundant wording; immediately states action and optional filter.

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?

Despite an output schema, the description omits parameter semantics and behavioral context (e.g., limit default, q, file requirement), leaving agent to infer how to invoke correctly.

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 space_name is partially explained by 'filtered by Space'; q, limit, and excel_path are left undefined, and schema has no descriptions, so meaning is mostly inferred from names.

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 clear action ('List') and resource ('components') with optional Space filtering. Does not explicitly mention Excel/COBie source, but excel_path parameter implies it; still distinguishable from graph-centric sibling tools by Space filter.

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 guidance on when to prefer this tool over siblings like graph_list_components_by_space or lookup_component_location; no mention of prerequisites or alternative selection criteria.

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