Create Custom Tab

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds context about the tab's UI placement and the requirement for custom object accessibility, but does not disclose additional behavioral traits such as permission needs or update semantics. This adds value but is not rich.

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 two sentences, front-loaded with the verb and resource, and wastes no words. It efficiently conveys purpose and a key requirement.

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?

With no output schema, the description doesn't need to detail return values, and annotations cover safety. However, the tool's schema also supports web and Visualforce tabs (url/page fields), which the description omits entirely. This narrows the tool's capabilities, making the description incomplete for all possible use cases.

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 100%, so all parameter meanings are already in the schema. The description references 'object API name' and 'motif' with an example, which matches schema entries but adds no new meaning beyond what is already structured.

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 specific action ('Creates a Custom Tab for a custom object'), the resource type, and its purpose ('appears in the navigation bar and App Launcher'). It distinguishes this from sibling tools by focusing on custom tabs for custom objects, making it unambiguous.

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 provides clear context for when to use this tool: 'Tabs are required to make custom objects accessible from the UI.' It implies the use case but does not explicitly list alternatives or exclusions, which keeps it just below a 5.

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