Custom Manage

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

With no annotations, the description must disclose behavior. It explains that params are forwarded unvalidated, that op and session_id remain top-level, and mentions the canonical call shape. It doesn't detail error handling or side effects, but the key behavior (unvalidated forwarding) is disclosed.

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 well-structured, starting with the core purpose, then usage details, then canonical shape. It uses bullet-like phrasing and packs information efficiently, with minimal redundancy.

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 the tool's complexity (op-based, with dynamic params), the description covers essentials: both operations, parameter requirements, canonical call shape, batch integration, and preference for first-class alternatives. The output schema is present, so return format isn't needed. Overall, this is a comprehensive definition.

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 0% coverage, but the description partially compensates by explaining the 'params' parameter and that op has enum values. However, it does not explain the session_id parameter beyond mentioning it is top-level, and the flexible params object needs more detail about how it is used.

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 lists or invokes custom tools from third-party addons. It distinguishes itself from sibling tools by focusing on custom addon tools, which is unique among the listed siblings.

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?

The description gives explicit guidance on when to use op='list' vs op='invoke', how to address custom tools in batch_execute, and notes that some custom tools are registered first-class and should be preferred. This is excellent usage guidance.

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