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

Annotations already declare the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false). The description adds genuinely new behavioral context by disclosing that MCP approval requirements are org-configurable while business workflow approvals always apply — useful, though it never says who approves, what happens on rejection, or whether the call blocks.

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?

Only two sentences, so there is no padding, and the create action is front-loaded. But the second sentence is generic approval boilerplate that could apply to any mutation tool in this catalogue, so the brevity comes at the cost of specificity rather than from tight writing.

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?

A mutation tool with a nested object parameter, no description coverage, and implicit scoping (no parent deal/site identifier in the schema) — the description should clarify what context the new tab is created under and how it relates to diligence fields. An output schema exists, so return values needn't be covered, but the creation context gap 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% and the description says nothing about the single nested `data` object or its name/sortOrder/description fields. The field names are largely self-explanatory, but nothing explains constraints like the 10,000-character limit, whether name must be unique, or how sortOrder is interpreted.

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?

"Create diligence_tab" is essentially the tool name restated; the only addition, "using the same business service as the screen," is opaque implementation language an agent cannot act on. It never explains what a diligence tab is or how it differs from siblings like create_diligence_field, update_diligence_tab, or list_diligence_tab.

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 on when to create a tab versus update an existing one, or on prerequisites (which deal/project/site the tab attaches to). The only usage-adjacent statement is that approvals may be required, which is a constraint rather than a selection rule.

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