remove_parameter

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

Without annotations, description effectively discloses refusal behavior based on references and force option. Success behavior is implied but return value not specified.

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 concise sentences with key details front-loaded. No extraneous 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?

Adequate for a simple removal tool with 3 params and no output schema. Covers main behavior and edge case, but lacks details on success output.

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?

Name and force are explained via context, but path is not described. With 0% schema coverage, some gaps remain despite partial compensation.

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?

Specific verb 'Remove' and resource 'ReportParameter' clearly stated. Distinguishes from siblings by specifying the object type and behavior.

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?

Clear context for use (removing parameters) and when to avoid (if referenced) with alternative force flag. No explicit mention of when to use other tools, but siblings are distinct.

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