CreateView

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

No annotations exist, so description must carry burden. It merely says 'Creates the view object in initial state' but provides no detail on side effects (e.g., whether activation is needed, transport behavior, required permissions, or impact on existing objects).

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 repetitive ('Operation: Create. Subject: View. Will be useful for creating view.') and could be condensed to a single sentence without loss. The first two sentences are essentially redundant.

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?

Lacks context about the lifecycle (e.g., need for activation, transport handling, initial state details) and does not explain return values or side effects. Incomplete for a creation tool with no output schema.

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 covers all 4 parameters with descriptions, achieving 100% coverage. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 it creates a 'CDS View or Classic View' but repeats 'create view' tautologically ('Operation: Create. Subject: View. Will be useful for creating view.'). It fails to distinguish from sibling Create* tools like CreateTable or CreateFunctionModule.

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 use this tool versus alternatives (e.g., CheckView, ActivateView, UpdateView). No mention of prerequisites, preconditions, or postconditions.

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