Create Gestoria Template

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

The description adds significant behavioral context: variable interpolation, due date offset behavior, attachment requirement, and an example. Annotations are minimal, so the description carries the burden and does it well.

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 concise with two sentences and an example, but the example is inline and could be more structured. Still efficient and informative.

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?

Despite having an output schema, the description is complete for a create tool: it covers core functionality, usage, parameters, and behavioral details. No 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 coverage is 100%, but the description adds value by explaining parameters in context (e.g., dueDateOffsetDays meaning, attachmentRequired default) and provides an example that ties all parameters together.

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 'Create a reusable document request template that the gestor can bulk-send to many client workspaces,' specifying the verb and resource, and distinguishes from siblings like gestoria_template_bulk_send.

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 explains when to use the tool (creating templates for bulk-sending) and provides an example, but does not explicitly state when not to use or list alternatives beyond implying the send tool.

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