net_create_rpc_event

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

There are no annotations, so the description bears the full burden of explaining behavior. It says 'Create or update' but does not disclose whether this replaces an existing event, whether it requires specific permissions, whether compilation/saving is automatic, or how reliability/replication behavior is affected. The boolean parameters save, compile, and reliable are present in the schema but their behavioral implications are not explained.

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 compact and front-loaded with the main purpose, followed by supporting details, a KB pointer, and a useful example. Each sentence contributes; the example is especially valuable for showing the required arguments. A small amount of formatting friction exists with the embedded code block, but it is acceptable.

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?

For a mutation tool with 8 parameters, no annotations, and an output schema not shown here, the description leaves important gaps: no guidance on duplicate event handling, no relationship to sibling networking tools, and no explanation of what 'Blueprint RPC' creation entails beyond the rpc_type enum. The example and KB link help, but an agent would likely need follow-up questions before invoking this confidently.

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?

With 0% schema description coverage, the description compensates for key parameters: it enumerates valid rpc_type values and gives a concrete JSON example for inputs. However, it leaves save, compile, reliable, and node_position undocumented, and those are not self-evident beyond their schema titles.

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 a specific verb and resource: 'Create or update a Custom Event as a Blueprint RPC.' This is clear and concrete. It does not explicitly contrast itself with sibling tools like net_configure_rpc or net_set_function_rpc, but the focused resource and action are enough to make the purpose unambiguous.

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?

Usage is implied through the example and the 'Create or update' phrasing, and the supported rpc_type values give practical guidance. However, the description never says when to choose this tool over closely related siblings such as net_configure_rpc or net_set_function_rpc, nor does it give exclusions.

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