RuntimeCreateProfilerTraceParameters

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

No annotations exist, and the description only states creation and return of a URI. It does not disclose side effects, authentication requirements, rate limits, or what happens to the created parameters. The behavioral transparency is minimal.

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 a single concise sentence that front-loads the core action and output. However, it could be restructured to include more detail without losing conciseness.

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 and no output schema, the description is severely incomplete. It does not explain parameter choices, the returned profilerId's purpose, or how to use it with other tools. The agent lacks sufficient information to correctly invoke the tool.

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?

Only 1 of 14 parameters (description) is described in the schema. The description does not explain any of the other 13 boolean or number parameters (e.g., all_misc_abap_statements, sql_trace). This fails to add meaning beyond the bare schema types.

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 tool creates profiler trace parameters and returns a profilerId URI. It distinguishes from other runtime tools by focusing on parameter creation, but does not contrast with similar profiler tools like RuntimeRunClassWithProfiling.

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 explicit usage guidelines or alternatives are provided. The description implies usage when setting up a profiled execution, but does not mention when to use this tool versus other profiler tools or how to select parameter values.

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