boj_cartridge_invoke

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It mentions 'invoke' and 'send a command,' implying a write/mutation operation, but does not disclose permissions, side effects, error handling, or response format. This is inadequate for a tool that likely performs actions with potential consequences.

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 brief (two sentences) and front-loaded with the core action. It avoids redundancy, though it could be more informative without sacrificing 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 no annotations, no output schema, and a tool that likely performs operations (implied by 'invoke'), the description is incomplete. It lacks details on behavior, return values, error cases, or how it fits with siblings, leaving significant gaps for an agent to use it correctly.

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 100%, so parameters 'name' and 'params' are documented in the schema. The description adds no extra meaning (e.g., examples of cartridge names or param structures), but the baseline is 3 since the schema handles parameter documentation adequately.

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 states the tool 'invoke[s] a BoJ cartridge operation' and 'send[s] a command to a specific cartridge for execution,' which clarifies the verb (invoke/send) and resource (cartridge). However, it lacks specificity about what 'invoke' entails (e.g., running a script, querying data) and does not differentiate from siblings like 'boj_cartridge_info' or 'boj_cartridges,' making it vague in context.

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 is provided on when to use this tool versus alternatives. The description mentions sending a command to a cartridge but does not specify scenarios, prerequisites, or exclusions compared to sibling tools (e.g., 'boj_cartridge_info' for metadata). This leaves usage unclear.

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