import_appliesto_function

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

Annotations already indicate the tool is a non-read-only, non-idempotent write operation, so the description's main additional value is the explicit auth requirement ('requires write permission') and the JSON input format. It does not detail overwrite or conflict side effects, but the annotations cover the core safety profile. No contradiction with annotations.

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?

A single, front-loaded sentence states the action, resource, input format, and permission need. There is no filler or redundant restatement of the tool name. This is an appropriate size for a simple import operation.

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 description and schema cover the basic invocation surface, and the annotations provide the safety profile. However, there is no output schema and little guidance on what the nested AppliesTo function JSON should contain, nor on default conflict behavior. These gaps make it minimally complete rather than fully self-contained.

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?

Every parameter is already described in the schema (100% coverage), so the description carries little parameter burden. It adds no extra meaning about definition structure, handle_conflict values, or fields_to_preserve semantics. Baseline 3 applies because the schema does the heavy lifting.

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 uses the specific verb 'Import' with the resource 'AppliesTo function' and the source format 'from JSON'. This clearly differentiates it from sibling import tools such as import_datasource or import_logsource. No ambiguity about what resource is operated on.

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?

There is no explicit statement of when to choose this tool over alternatives, and no mention of alternative tools. The usage is only implied by the resource name and purpose, though the permission prerequisite ('requires write permission') provides some selective context. This meets the 'implied usage' level.

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