set_tab_definition

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'configure tab stops' and does not reveal what happens when tab_stops is null, whether existing tab stops are replaced or merged, or what side effects occur on the document. This is a mutation operation with minimal behavioral context.

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 and is front-loaded with the action and target. It contains no filler or redundancy, though its brevity contributes to the lack of detail scored elsewhere.

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 configuration tool with no annotations, the description is under-specified: it does not define what 'current paragraph' means, how tab stops should be structured, or what null means. The presence of an output schema reduces the need to describe return values, but the missing operational context is significant.

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 the description must compensate, but it only mentions 'tab stops' generically. It does not explain the required doc_id parameter, the structure of tab_stops objects, or the meaning of the null default. The description adds only minimal context over the raw schema.

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 ('Configure') and resource ('tab stops') and scopes it to the current paragraph, which allows an agent to see this is a paragraph-level tab-stop operation. It does not explicitly distinguish it from siblings like set_section_definition or set_paragraph_style, but the resource 'tab stops' is distinct enough to establish purpose.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisite conditions, and no exclusion criteria. The phrase 'for current paragraph' implies a context, but the description does not clarify how that context is determined or when this tool should be preferred over related formatting tools.

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