add_title_block

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

There are no annotations, so the description carries the full behavioral burden. It states the additive action but does not disclose what happens if a title block already exists, whether omitted fields are left blank or reset, or how the target sheet is selected. This is a meaningful gap for a mutation 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?

A single, front-loaded sentence that names the action, the target, the precondition, and the parameter behavior. There is no redundant or filler content.

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 9 optional parameters, no annotations, and the sibling update_title_block, the description is too thin. It does not explain how the target sheet is identified, prerequisites, failure behavior, or the relationship to update_title_block, leaving an agent with significant uncertainty about correct invocation.

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% across 9 parameters, and the descriptions only add 'fill the given fields,' which does not explain formats, units, or meaning beyond the property titles. The property names are somewhat readable, but the description fails to compensate for the complete lack of schema-level documentation.

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 uses a specific verb ('Add') and resource ('title block/cartouche') and clarifies the exact scope: adding to a sheet created without one. This distinguishes it from the sibling update_title_block, which would apply when one already exists.

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 phrase 'created without one' provides a clear precondition and implies that update_title_block is the appropriate alternative for existing title blocks. It does not explicitly mention alternatives or exclusions, but the usage context is clear enough for an agent to route correctly.

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