rhino_drawing_title_block_add

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

The description only indicates a write operation ('Add'), which aligns with readOnlyHint=false. It omits details about side effects, permissions, or whether the title block replaces an existing one, adding little beyond the annotation.

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 with no fluff. It is front-loaded with the action and lists the components efficiently, earning its place.

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 tool's complexity (many parameters, combined operation), the description is too brief. It ignores the output schema, leaves prerequisites unstated, and fails to contextualize the return value, resulting in significant gaps.

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 description provides no information about the input parameters, despite a complex schema with many required fields. With 0% schema description coverage, the description fails to compensate, leaving the agent uninformed about required arguments like sheet_id, project, title, and date_iso.

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 adds a bottom-right title block, north arrow, and scale bar to a sheet. It uses specific verbs and resources, distinguishing itself from sibling tools that handle these elements individually.

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 provided on when to use this tool versus adding the components separately or prerequisites like an existing sheet. The description leaves the user to infer usage from context.

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