import_bpa_ruleset

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

With no annotations, the description fully carries the behavioral disclosure burden. It explicitly states that rules matching built-ins are mapped to evaluable checks, unsupported C#/LINQ expressions are registered as descriptive-only and flagged, and the arbitrary TE expression string is never executed. This safety-critical transparency is exceptional and goes beyond what annotations typically provide.

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?

The description is a single, information-dense sentence that front-loads the primary action. Every clause contributes meaning: the import, the reconciliation logic, and the explicit non-execution safety guarantee. It is slightly long but not verbose, earning a 4 for clarity and focus.

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?

The tool has only two parameters, no output schema, and no annotations. The description covers the essential behavior: what is imported, how rules are categorized, and a critical safety guarantee. It does not detail return values or error scenarios, but given the tool's complexity, the coverage is strong. A 4 reflects the solid but not exhaustive completeness.

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?

The schema covers the 'json' parameter with a description, but 'sessionId' is undocumented (50% coverage). The description clarifies the json input's role as a BPARules.json document and explains the reconciliation behavior, but it does not compensate for the missing sessionId semantics. The behavior described is tool-level rather than parameter-level, so it adds modest value beyond the schema.

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 a specific action: 'Import a Tabular Editor BPARules.json document and reconcile it with the built-in catalogue.' This distinguishes it from sibling tools like list_bpa_rules, run_bpa, and fix_bpa by focusing on the import/reconciliation workflow. The mapping to evaluable checks and descriptive-only rules further clarifies its unique role.

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 implies when to use the tool: when you have a BPARules.json document to import and reconcile. It does not explicitly name alternatives or exclusions, but the import/reconcile context is clear enough to differentiate from related BPA tools. A 4 is appropriate because it lacks explicit 'when not to use' guidance.

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