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

Annotations already mark this as read-only and idempotent, but the description adds substantial behavioral detail: the exact nested response shape, the caller's access level, error conditions for unknown or invisible ids, the permission semantics of visibility, and the fact that this tool never returns null. This goes well beyond the annotation baseline.

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 dense but every sentence earns its place. It front-loads the core purpose and return-nesting warning, then covers access levels, error/visibility semantics, null behavior, and the relationship to template.set_entries without repetition. The structure guides an agent from immediate invocation details to edge-case behavior.

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?

For a single-parameter read tool with no output schema, the description is remarkably complete. It covers return shape, access semantics, permission boundaries, error behavior, and the important workflow of reading before template.set_entries. Nothing an agent needs to call this correctly is missing.

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 input schema already fully documents the single `id` parameter with its format (`tpl_…`) and source (template.list), so the description adds little parameter-level meaning. It mentions using the id as template_id for toolbox.createtons, but that is more about downstream authorization than the parameter itself.

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 opens with a specific verb and resource: 'Read one template definition and its entries.' It clearly identifies this as a single-item read and later contrasts it with role.get/team.get/governance reads, distinguishing it from sibling tools even without seeing their schemas.

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 'Always read this before template.set_entries,' giving a concrete workflow where this tool is required. It also explains how the returned `access` value ('use') authorizes toolbox.create, and contrasts the null behavior with role.get/team.get so an agent knows when not to expect a null result.

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