create_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. It only says 'Create', implying a mutation, but does not disclose side effects, required parent existence, error behavior, or reversibility. For a write operation with zero annotation coverage, this is a significant gap.

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 short sentence, which is structurally efficient and front-loaded. However, it is under-specified, so while conciseness is achieved, it sacrifices necessary content. It is not the concise-but-complete ideal.

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?

The tool is simple with two parameters and has an output schema, so return values are covered. But it omits crucial context: whether parent_id must exist, what happens on duplicate names, validation rules, or any side effects. Given no annotations, the description is incomplete for an agent to call correctly.

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 description coverage is 0%, so both parameters (name, parent_id) are entirely undocumented in the schema. The description adds no meaning beyond the parameter names—it doesn't clarify what parent_id refers to, any format constraints, or relationships. The description fails to compensate for the schema's lack of detail.

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 states a specific verb ('Create') and resource ('SysML v1 Block') with a location constraint ('under parent_id'). It is clear about what it does and can be distinguished from many sibling create_* tools by the element type, though it doesn't explicitly contrast with similar tools like create_interface_block.

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 given on when to use this tool versus alternatives. There are numerous create_* siblings, and the description provides no criteria for selection, no prerequisites, and no exclusions.

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