create_schema

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

Annotations indicate readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the description needed to add behavioral context such as side effects, required permissions, or what 'create' implies. It only says 'Create a new extraction schema' and adds nothing beyond the annotations. No contradiction exists, but no value is added.

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 sentence with no filler or redundant phrases. It is as concise as possible while conveying the basic purpose.

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 5 parameters, a nested config object, no output schema, and no usage guidance. The description is far too sparse to give an agent enough context to invoke the tool correctly, especially for parameters like fix, test, and extract_prompt.

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 only 20% schema description coverage, the description needed to compensate by explaining parameters like name, config, extract_prompt, fix, and test. It provides no parameter-level meaning whatsoever, leaving agents to guess the roles of most fields.

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 clear action and resource: 'Create a new extraction schema for structured data extraction.' It is specific enough to distinguish from update/delete/list operations on schemas, though it does not explicitly differentiate it from create_config or other sibling tools.

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 gives no guidance on when to use this tool versus alternatives like create_config, update_schema, or list_schemas. There is no mention of prerequisites, exclusions, or context that would help an agent choose this tool over siblings.

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