Create Managed Object Definition

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

The description adds context beyond annotations by noting that creation appends to the managed config and requires prior schema understanding. Annotations already indicate non-destructive (destructiveHint: false) and open world (openWorldHint: true), and the description aligns with these without contradiction.

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 consists of two concise sentences with no redundant information. It front-loads the purpose and immediately provides an important usage note, making it efficient and easy to parse.

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 lack of an output schema, the description covers the essential usage context: what the tool does, the prerequisite step, and the required parameters. It could be improved by mentioning what success looks like (e.g., returns the created definition ID) or error conditions, but the annotations and schema fill in some gaps.

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%, with both parameters having clear descriptions. The tool description reinforces the schema's suggestion to use getManagedObjectSchema for the objectDefinition structure but does not add new semantic meaning beyond what the schema provides. Therefore, a baseline score of 3 is appropriate.

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 it creates a new managed object type definition, specifying the action 'create' and the resource 'managed object type definition'. It distinguishes from sibling tools like createManagedObject (creates an instance) and other create tools, making the purpose unambiguous.

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 explicitly instructs to call getManagedObjectSchema with includeFullDefinition=true first to understand the expected structure, providing a clear prerequisite and usage sequence. However, it does not explicitly state when not to use the tool or mention alternative tools.

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