create_block

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

No annotations are provided, so the description must carry the behavioral burden. It transparently says the tool creates a block, which implies a write operation but doesn't disclose side effects, error conditions, or whether existing content in the page is modified. The description is minimal but not misleading; it just lacks depth about what 'create' entails in Logseq.

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?

At six words, it is extremely concise and front-loaded. Every word carries meaning, and there is no filler. However, it is so brief that it doesn't provide any context beyond the tool name's obvious meaning.

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 write operation with no output schema and no annotations, the description is thin. It doesn't explain the expected page identifier format (name vs UUID), whether properties are optional or how they are structured, whether parent_block_id must reference an existing block, or what success/failure looks like. The tool's complexity (4 params, nested objects) demands more guidance than this single sentence 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?

Schema coverage is 100%, so the schema documents all parameters with descriptions. The description adds no parameter detail beyond what's in the schema, but baseline 3 applies because the schema already covers the semantics of page, content, properties, and parent_block_id. The description doesn't clarify the format of properties or parent_block_id relationships, but with full coverage, that is acceptable.

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 says 'Create a new block in Logseq', which is a specific verb and resource, and it is distinguishable from the closely related update_block and create_page. However, it doesn't elaborate on what creating a block entails or how it differs from create_page beyond the resource type, which is already evident from the names.

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. It doesn't mention that create_page is for pages while this is for blocks, nor does it state any prerequisites like needing an existing page or page identifier format. An agent is left to infer usage context from the parameter names.

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