set_extraction_schema

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

Lacks annotations, so description must fully disclose behavior. It mentions 'Enable extraction immediately' via 'enabled' parameter but does not explain overwriting behavior, required permissions, rate limits, or side effects of setting a schema.

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?

One-sentence purpose followed by a clean parameter list. No extraneous text; every element serves a 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?

Given the complexity (6 params, 4 required, no annotations, has output schema), the description covers parameter semantics but omits return value details, error handling, and idempotency. Adequate for basic usage but incomplete for robust invocation.

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 0% schema description coverage, the description adds value by providing docstrings for all 6 parameters, including clarifying 'schema' as a JSON string of a valid JSON Schema object and explaining 'enabled' default behavior. Only minor details missing (e.g., constraints on domain_id).

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 explicitly states 'Set structured extraction schema for an inbox,' with a clear verb (Set) and resource (extraction schema). It distinguishes from sibling 'remove_extraction_schema' by focusing on setting rather than removing.

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?

No guidance on when to use this tool versus alternatives (e.g., remove_extraction_schema). No context about prerequisites, typical use cases, or conditions where setting a schema is appropriate.

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