send_request

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only mentions environment defaults and token requirements, but does not state whether the tool is idempotent, destructive, rate-limited, or any side effects. The term 'real pylzt request' is vague.

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 very short (one sentence), which is concise, but it sacrifices necessary details. For a tool with multiple parameters and no annotations, the description should be longer to compensate.

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 has 4 parameters (including a nested object), an output schema, and no annotations, the description is severely incomplete. It does not explain how to use the tool, what the parameters do, or what the output looks like. The agent would struggle to invoke 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?

The schema has 4 parameters and 0% description coverage. The description does not explain any parameter beyond implicit reference to 'token' and 'target'. It fails to clarify the structure of 'params' or the meaning of 'method_name'. The description adds no value over the schema.

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 action ('send') and the resource ('real pylzt request'), and distinguishes between testnet and prod environments. However, it does not differentiate from sibling tools like 'get_run' or 'create_subscription', missing an opportunity to clarify that this is a low-level generic request sender.

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 a minor hint about environment selection ('defaults to testnet, prod requires a token'), but provides no guidance on when to use this tool versus alternatives. Sibling tools cover specific operations, and the description should clarify that this is for arbitrary requests not covered by other tools.

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