Create New Sub Cost Catalog

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

Annotations already indicate read-only and destructive hints, but description adds behavioral context: the level constraint, that it returns the created object on success, and specifies the HTTP 201 status. No contradictions.

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?

Four sentences, front-loaded with key constraint, efficient. No redundant or vague phrasing.

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?

Covers core creation behavior and required parameters. Lacks details on error responses or edge cases, but for a simple create tool with no output schema, it is adequately complete.

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 covers 100% of parameters, but description adds value by explaining URL path parameter placement (catalog_id, company_id) and indicating that 'name' is a JSON request body field, which is not evident from schema alone.

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 verb 'create' and resource 'new Cost Catalog records', with additional constraint 'only one level sub-catalog'. It effectively distinguishes from siblings like 'create_catalog' by specifying it's for sub-catalogs.

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?

Mentions the level constraint and required parameters, but lacks explicit guidance on when to use this versus alternative tools (e.g., 'create_catalog'). No exclusion criteria or alternatives provided.

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