create_suite

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

No annotations are provided, so the description carries the full burden. It does not disclose side effects, error behavior, idempotency, or what happens if the suite already exists. The only transparency is the schema's note that dataset_handle is unused, but the description itself offers little beyond the basic create action.

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 clear, front-loaded sentence conveys the core purpose without wasted words. It is appropriately sized for a simple create 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 tool is simple, all parameters are fully described in the schema, and an output schema exists. The description is sufficient for basic usage, though it could mention behavioral outcomes or prerequisites for 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?

Schema description coverage is 100%, so the baseline is 3. The description adds 'optionally profiled from a dataset,' but this is already reflected in the profiler parameter. It does not clarify the deprecation or the unused nature of dataset_handle beyond what the schema already states.

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?

Description uses a specific verb ('Create') and resource ('named ExpectationSuite'), clearly distinguishing from siblings like add_expectation. It also mentions optional profiling, which adds useful scope.

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 the tool is for creating a new suite, optionally with profiling, but offers no explicit guidance on when to use it versus alternatives like add_expectation or run_checkpoint. There is no exclusion or alternative tool mention.

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