RuntimeCreateProfilerTraceParameters

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

No annotations provided, so description must disclose side effects. It only states creation and return of a URI, but does not mention if this is destructive, requires permissions, or the lifecycle of the parameters.

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?

Single sentence is under-specifying for a complex tool. It lacks structure to convey multiple aspects (parameters, usage, behavior) and misses key information.

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?

Given 14 parameters, no annotations, and no output schema, description is severely incomplete. Does not explain return value format, parameter details, or usage context, making it inadequate for proper agent invocation.

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 has 14 parameters with only 7% description coverage. Description adds no parameter explanations beyond the schema. It fails to compensate for low schema coverage.

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?

Description clearly states the action (create), resource (ABAP profiler trace parameters), and output (profilerId URI). It distinguishes from sibling tools like RuntimeAnalyzeProfilerTrace which analyze existing traces.

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 like RuntimeRunClassWithProfiling. Does not explain prerequisites, recommended workflow, or context for invoking the tool.

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