import_nrsdk

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

Annotations indicate a non-read-only, potentially side-effect operation. The description adds that the tool 'configures initial SDK settings after import', which provides behavioral context beyond the annotations. It does not detail what settings or potential destructive actions, but the added context is valuable.

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 clear sentences, no wasted words. The first sentence states the core purpose, and the following sentences add significant detail efficiently. Perfectly front-loaded.

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 complexity and rich input schema, the description covers the essential aspects (import, source options, configuration). It does not mention return values or error behavior, but for an import tool, the purpose and parameters are sufficiently clear. The annotation 'openWorldHint' hints at side effects, which the description acknowledges.

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?

With 100% schema coverage, the baseline is 3. The description adds meaning by explaining the two import modes ('local' vs 'url'), which maps to the 'path' and 'url' parameters, and the optional import of examples and streaming assets. This goes beyond the schema's descriptions.

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?

The description clearly states the verb 'Imports' and the resource 'NRSDK (XREAL SDK)', and distinguishes two import modes (local file or download). It sets the tool apart from siblings like 'setup_xreal_project' or 'add_package' by focusing specifically on importing and configuring the NRSDK.

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 description explicitly mentions two import sources (local file or download a specific version), giving clear context on when to use each. However, it does not exclude alternatives or provide when-not-to-use guidance relative to sibling tools, which would improve the score.

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