bricks_get_stats

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

The description correctly indicates a read-only operation ('Get site-wide statistics'), and lists the returned data. No side effects or permissions are mentioned, but given the tool's simplicity and lack of destructive potential, this is adequate. The absence of annotations does not create a contradiction.

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 that front-loads the main purpose and lists all relevant statistics. There is no redundant information, making it highly concise and structured.

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?

Given the tool has no parameters and no output schema, the description provides a reasonable level of completeness by listing the statistics. It could be improved by mentioning the return format (e.g., 'returns a JSON object'), but the current description is sufficient for an agent to understand what the tool provides.

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 has no parameters, and schema description coverage is 100% (empty). The baseline for zero parameters is 4; the description does not need to add parameter details. It could have explained the output format, but that is not required for this dimension.

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 retrieves site-wide statistics and enumerates the specific metrics (pages, templates, etc.). It uses a specific verb ('Get') and resource ('site-wide statistics'), distinguishing it from sibling tools like bricks_list_pages which list individual items.

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 does not explicitly state when to use this tool versus alternatives. Usage is implied (get overall stats), but no guidance is provided on when not to use it or which sibling tools might be more appropriate for specific needs.

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