bricks_get_template

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

Description indicates it returns 'element tree with all settings', implying a read operation with no side effects. However, without annotations, it does not disclose potential performance implications, required permissions, or whether the output is paginated or complete. Some transparency exists but is minimal.

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?

Two sentences, concise and front-loaded. No redundant or unnecessary wording. Every word earns its place.

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 simple retrieval tool with one parameter and no output schema, the description is adequately informative. It tells what it does and what it returns. However, it lacks usage guidance and could elaborate on the structure of the returned data. Still, it is mostly complete for a basic tool.

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 only parameter 'template_id' is described in the schema as 'Template ID'. The description adds no additional meaning or usage context beyond what the schema provides. With 100% schema coverage, baseline is 3.

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 the tool 'Get the full Bricks Builder data for a specific template' with a specific verb and resource. It distinguishes itself from siblings like 'bricks_get_page' (getting page data) and 'bricks_list_templates' (listing templates).

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 on when to use this tool versus alternatives. For example, it does not clarify when to use 'bricks_get_template' over 'bricks_get_page' or 'bricks_search_templates'. Context is implied but no exclusions or prerequisites are mentioned.

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