post-crm-object-schemas-v3-schemas_schemas

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It simply says 'create a new schema' without mentioning irreversibility, permissions, side effects, or consequences. This is a serious gap for a mutation tool of this complexity.

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 and front-loaded with the primary action. However, the second sentence is a lazy pointer to the input schema, and the overall content is under-specified. It is concise but lacks the substance needed to stand alone.

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 9 parameters, nested objects, and no output schema, this tool requires substantial contextual guidance. The description does not explain how to construct a valid schema, when to use it, or what the response will look like. It is incomplete for an agent to operate effectively.

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%, and the input schema provides detailed descriptions for all parameters. The description adds no new parameter information beyond pointing to the inputSchema, so it stays at the baseline for high coverage.

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 'Create a new schema,' which is a specific verb+resource. The tool name confirms it is for posting CRM object schemas. However, it does not explicitly differentiate from sibling tools like the association schema creation tool, so it is clear but not fully disambiguated.

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 when-to-use guidance is provided. The description does not mention alternatives among the many schema-related siblings, nor does it specify contexts where this tool is appropriate. The only instruction about the body parameter is not usage guidance.

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