schema_generate_tab

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds no behavioral context beyond the safety profile — nothing about overwrite behavior on existing tab files, prerequisites, or side effects when the directory already contains files. The 'generate' framing is consistent with the annotations, so no contradiction, but little value is added.

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?

Two short sentences, front-loaded with the action and the output artifact. The second sentence is slightly peripheral (a definition of custom tabs) but earns its place by clarifying the artifact for an agent unfamiliar with the Salesforce concept.

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 generation tool with no output schema and full annotation coverage of the safety profile, the description covers purpose but omits prerequisites and what is actually written/returned. Adequate to invoke, but an agent must infer project context and overwrite semantics.

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 nested schema documents all three fields (icon range 1-100 with color/icon semantics, object API name with the MyObject__c example, directory path), so the schema carries the semantic load and the description adds nothing. The top-level 'input' wrapper itself is undescribed, but the meaningful parameters are covered, which keeps this at the baseline 3.

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?

States a specific verb (Generate) and resource (metadata source files for a custom tab on a custom object), so an agent knows exactly what it produces. No sibling generates tabs, so differentiation is moot, but the second sentence explaining what custom tabs are is competent domain framing rather than a restatement of the name.

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 gives no when-to-use, no when-not-to-use, and no prerequisites (e.g., must be inside a Salesforce DX project, must reference an existing custom object). It implies the tool creates a tab for a custom object but never states the conditions that select it over manual metadata authoring or the other generate_* siblings.

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