Server Quality Checklist

Tool Scores

• lumics_get_meA
  4.4/5.0
  Behavior5/5

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

  Beyond the annotations (readOnly, idempotent, etc.), the description discloses the conditional tool registration behavior and explains that passing a companyId argument won't help because the tools are absent rather than failing. This is valuable context not evident from structured data.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a multi-sentence paragraph but front-loads the core function. The bootstrap explanation adds length, yet every sentence serves a purpose. It is not overly verbose and is well-structured.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a tool with one optional param and no output schema, the description is remarkably complete: it explains the primary return fields, the bootstrap scenario, the environment variable setup, and the credential check use case. The 'fields' parameter is handled by the schema, so no gap remains.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters2/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema fully describes the optional 'fields' parameter, so the baseline is 3. However, the description states 'Takes no arguments' which directly contradicts the existence of this optional parameter and could mislead an agent into thinking it cannot pass arguments to control output. This actively worsens parameter understanding.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  Clearly states it returns the authenticated Lumics user and their company, listing specific fields (id, name, IANA timezone, active flag). This easily distinguishes it from the sibling tool about device definition components.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines5/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Explicitly explains when this tool is essential: when LUMICS_COMPANY_ID is not set, company-scoped tools are not registered, so this may be the only tool available. It instructs to call it first and tells the operator to set the environment variable, and also positions it as the cheapest way to check credentials.

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

• lumics_get_device_definition_componentsA
  4.9/5.0
  Behavior5/5

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

  Even though annotations already declare readOnlyHint=true and destructiveHint=false, the description adds substantial behavioral context: the payload is large, accepts no limit, is platform-wide (same for every company), takes no company id, and its schema is the inventory schema with no metric property names. No contradictions exist.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is long but every sentence carries meaningful information: purpose, structural details, usage warnings, alternative tool suggestions, and a derived itemType example. It is front-loaded with the primary purpose and flows logically.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness5/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  With no output schema, the description fully explains the returned structure (filePath, data block, schema field), the itemType composition rule (filePath + data.itemType), the platform-wide scope, and the large size/no-limit caveat. It also provides alternative tool recommendations. This is highly complete for a read-only metadata tool.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema already provides a full description of the 'fields' parameter (100% coverage). The description adds practical guidance with a concrete example ('fields' e.g. ['filePath']) and explains why to use it (to keep the response manageable). This goes beyond the schema baseline.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description explicitly states 'Return the platform-wide component definitions' and describes the exact structure (filePath, data block with fields like modelName, itemType, etc.). It clearly distinguishes this tool from siblings like lumics_get_me and from similar tools like lumics_get_metric_summary and lumics_list_component_types.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines5/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description gives explicit use cases: 'Use this when you need to know what fields a component type has or how it is defined.' It also provides clear exclusions and alternatives, such as 'do NOT use it to find values for a metric tool's properties argument' (use lumics_get_metric_summary) and 'if you only need a valid component type key for this tenant, call lumics_list_component_types instead.'

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