run_tool

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

No annotations provided, but description mentions 'governed, logged execution' and 'return JSON output', which adds behavioral context. However, does not detail side effects, error handling, or authentication needs.

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, front-loaded with the action, no wasted words.

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?

Has output schema so return values are covered, but description lacks prerequisites (e.g., tool must be approved) and does not clarify that input_json must match the tool's expected format. Could be more complete for a complex execution 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?

Schema description coverage is 0%, and the description provides no details about the parameters (tool_id and input_json). It only mentions 'JSON input' without explaining what the input should contain.

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 it executes an approved ToolForge tool, distinguishing it from siblings like register_tool, approve_tool, and list_tools. The verb 'Execute' and resource 'approved ToolForge tool' are specific.

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?

Explicitly says 'Use this when the correct approved tool has been selected and the task should be performed through a governed, logged execution.', providing clear context for when to use it and contrasting with other tools.

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