Create Template

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

Annotations indicate this is a non-readOnly, non-idempotent, non-destructive, openWorld operation. The description adds context by specifying what the template defines (property schema, allowed actions, access rules) and provides an example, which helps clarify the tool's behavior beyond annotations, though it doesn't detail side effects like authentication needs or rate limits.

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 front-loaded with the core purpose in the first sentence, followed by specifics and an example. It uses two concise sentences with no wasted words, effectively communicating key information without redundancy.

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 tool's complexity (5 parameters, nested objects, no output schema) and rich annotations, the description is reasonably complete. It explains the tool's purpose and provides an example, but could improve by detailing output behavior or error handling, though annotations cover safety aspects adequately.

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%, so parameters are well-documented in the schema. The description adds minimal semantic context by mentioning 'property schema, allowed actions, and access rules' and an example, but does not provide additional details beyond what the schema already covers, meeting the baseline for high schema 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 clearly states the verb ('Create') and resource ('new token template'), specifies what it defines ('structure of tokenized objects'), and distinguishes it from sibling tools like dual_create_template_variation or dual_update_template by focusing on initial creation of a template with property schema, actions, and access rules.

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 implies usage for defining tokenized object structures, but does not explicitly state when to use this tool versus alternatives like dual_create_template_variation or dual_update_template. It provides an example context but lacks explicit guidance on prerequisites or exclusions.

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