get_template_definition

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

With no annotations, the description carries the transparency burden. It clearly indicates a read-only operation ('Get') and describes the return structure ('roles, tabs, documents'), which is helpful. It does not discuss permissions or error cases, but the operation is simple and non-destructive, so this is acceptable.

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 compact and well-structured with a brief purpose, an Args section, and a Returns section. Every sentence adds value without unnecessary elaboration.

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?

The description clearly states what the tool does and what it returns, with a high-level summary of the output contents. Since an output schema exists, the agent can access detailed field information. The tool is simple, so the description is complete enough for selection and invocation.

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?

The schema has zero description coverage for the only parameter. The description adds meaning by stating 'template_id: The template ID to retrieve,' clarifying the parameter's role. This is sufficient for a single, obvious parameter.

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 uses a specific verb and resource: 'Get the definition and details of a specific template.' It clearly distinguishes this from sibling tools like list_templates or create_template by focusing on retrieving a single template's full details.

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 when a specific template ID is known, and it explains the required argument. However, it does not explicitly mention alternatives like list_templates or when not to use this tool, so the guidance is implicit rather than explicit.

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