Create a schema

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

The description identifies this as a save operation and mentions it is free, which is useful behavioral context beyond the openWorldHint annotation. But it does not disclose whether saving with an existing name overwrites, requires authentication, has side effects, or returns a schema ID. For a mutation tool with minimal annotations, those gaps are significant.

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 short, front-loaded with the core action, and contains no wasted sentences. The 'Free' fragment and the dense formatting tip are slightly abrupt, but both are useful and easy to scan.

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?

For a schema-creation tool with a nested JSON Schema parameter, the description covers the core purpose and gives basic shape guidance. It remains incomplete on persistence behavior, parameter meanings, and what the call returns, especially given the lack of an output schema and only minimal annotations.

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 only 33%, so the description must carry more of the parameter burden. It gives useful guidance for the json_schema parameter by recommending type object, property descriptions, and arrays of objects for line items, but it never mentions schema_name or the optional guidelines parameter, leaving two of three parameters unclear.

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 states a specific verb and resource: save a JSON Schema as a DocuPipe schema. It also explains the effect, making every extraction return consistent fields. It does not explicitly distinguish this from siblings such as list_schemas or extract.

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 phrase 'so every extraction returns the same fields' implies when this tool is useful, and 'Free' adds context. However, there is no explicit guidance on when to create a schema versus using extract directly, or whether to check existing schemas with list_schemas first.

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