bricks_get_template

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

No annotations are provided, so the description bears full responsibility. It states the tool gets details including elements, but it does not disclose that it is a read-only operation, any authentication requirements, or potential performance implications. The behavioral traits are only implicitly suggested.

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 a single sentence with no extraneous words. It efficiently communicates the core action and the key content returned (elements array). Could be slightly more structured but is appropriately concise.

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?

No output schema exists, so the description should explain return values. It mentions 'template details including its Bricks elements array' but omits other fields, error handling, or prerequisites. For a simple get tool with two parameters, this is adequate but not fully complete.

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% with descriptions for both parameters (site with defaults, template_id required). The description adds 'including its Bricks elements array' to the purpose but does not elaborate on the parameters themselves. Baseline of 3 is appropriate since the schema already documents parameters adequately.

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 'Get' and resource 'template details including its Bricks elements array'. It clearly differentiates from similar siblings like bricks_list_templates (list all) and bricks_create_template (create). However, it could be more explicit in distinguishing from bricks_get_element_tree or other get tools.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools (e.g., bricks_list_templates, bricks_get_element_tree), the description lacks context for choosing the right tool. There is no discussion of prerequisites or scenarios.

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