create_site_block

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Создать' (Create) implies a write/mutation operation, but the description doesn't disclose any behavioral traits such as permissions required, whether it's idempotent, what happens on failure, or what the output might look like. It lacks critical context for a creation tool.

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, concise sentence in Russian that directly states the tool's purpose without any fluff or unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity of a creation tool with 4 parameters, no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks essential details about behavior, parameters, and output, making it inadequate for an AI agent to use the tool effectively without additional context or trial-and-error.

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 4 parameters with 0% description coverage, meaning none are documented in the schema. The description provides no information about any parameters, not even hinting at what 'block_name', 'block_title', 'block_category', or 'webasyst_path' mean or how they should be used. This fails to compensate for the low schema coverage.

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 'Создать блок конструктора Site' (Create a Site constructor block) states a clear verb ('create') and resource ('Site constructor block'), which is better than a tautology. However, it's somewhat vague about what a 'Site constructor block' actually is, and it doesn't distinguish this tool from sibling tools like create_site_plugin, create_site_theme, or create_site_widget, which all appear to create different site-related components.

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 provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools for creating site-related components (e.g., create_site_plugin, create_site_theme, create_site_widget), but the description doesn't explain what makes a 'block' different or when it's appropriate. No prerequisites, exclusions, or context are mentioned.

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