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

The description discloses that schemas are validated before saving and that only successfully saved schemas are returned with their UUIDs. This adds context beyond the annotations (which already mark destructive and idempotent). It clarifies partial success behavior without contradicting any annotation.

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 well-structured: purpose statement, critical note, required fields, attribute types, optional parameter, and a comprehensive example. Each section adds necessary information without redundancy, and the most critical usage guidance is front-loaded.

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?

With no output schema, the description explains the return value (list of successfully saved schemas with UUIDs). It covers all required input structure, optional parameters, and edge cases like validation. An agent has all information needed to call this tool correctly.

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?

While the input schema only lists 'schemas' as an array of objects, the description details the internal structure of each schema object, including required fields, attribute types with concrete examples, and the flat vs. wrapped distinction. This significantly compensates for the schema's vagueness, despite 100% coverage of parameter names.

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 clearly states the tool's purpose: save/upload schemas to the domain, with validation and a return of successfully saved schemas with UUIDs. It distinguishes itself from sibling tools like schema_delete, schema_get, and schema_update by focusing on creation.

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?

Provides explicit usage guidance: 'Pass FLAT schema objects directly — do NOT wrap in schema_content', required fields, supported attribute types, and optional project_uuid. It gives clear instructions on how to invoke the tool correctly, even including a full example.

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