title_block

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

The description discloses that the tool reads the sheet size automatically and returns the measured border, which is useful behavioral context. However, it does not detail potential side effects or prerequisites, and there are no annotations to rely on.

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 two concise sentences that immediately state the purpose, then add relevant details about behavior. No wasted words.

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 description gives the core function and return value, but with 10 parameters and no parameter documentation, the agent lacks sufficient guidance for correct invocation. The output schema likely covers return, but parameter semantics are an important gap.

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?

With 10 parameters and no schema descriptions (0% coverage), the description does not explain individual parameters like border, binding, or revision. It only provides high-level context about sheet mm coordinates and bottom-right placement, leaving parameter meanings to inference from names.

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 draws a border and an ISO 7200 title block with specific dimensions and placement (180x40, bottom right). It also mentions reading sheet size and returning the measured border, distinguishing it from generic drawing tools.

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 implies usage for creating title blocks on sheets but does not explicitly state when to use this over alternatives. It mentions it reads the sheet size itself, suggesting sheet-level drawing, but no alternatives are referenced.

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