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

Beyond the readOnlyHint annotation, the description adds significant behavioral detail: the template id equals a model id, the guide is the live FINANCE.md rather than a snapshot, changes propagate live, and the operation is account-level and read-only. This tells an agent exactly what to expect and how the data relates.

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 not bloated; every sentence contributes a distinct fact. It is front-loaded with the core read operation. It is slightly longer than strictly necessary due to workflow guidance, but that content is useful rather than filler.

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?

With no output schema, the description carries the burden of explaining what the tool returns: the blueprint plus the markdown guide. It also covers id semantics, edit propagation, and post-fork steps, making the tool fully comprehensible for an agent to invoke and interpret.

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 documents template_id fully, including its source via layerz_list_templates. The description adds extra meaning by revealing that a template's id equals its model id, which helps an agent reason about id provenance and the relationship to FINANCE.md.

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 a specific action and resource: 'Read a template in full: its blueprint plus its description.' It defines what is included, distinguishes the return content from other getter tools, and uses a concrete verb rather than restating the title.

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 gives clear context for reading and applying templates, explains that editing the guide happens through layerz_set_finance_md, and advises updating the new model's FINANCE.md after forking or applying. It lacks an explicit 'when not to use' statement, but the usage context is strong enough.

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