orders_add_note

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that the tool requires a higher plan, which is a real behavioral constraint, but it says nothing about the side effects, permissions, or what happens when invoked. The tool's actual behavior remains opaque.

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 extremely short and front-loaded, immediately communicating the upgrade requirement. It is concise and the single sentence earns its place as a warning, though it sacrifices substantive purpose information for brevity.

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 that the tool has no parameters and no output schema, the main missing context is the tool's purpose and behavior. The description is complete only regarding the upgrade gate, but as a tool definition for an AI agent it is inadequate because it never explains what 'orders_add_note' does.

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 tool has zero parameters, so the baseline for parameter semantics is 4. The empty input schema provides no parameter details, and the description adds no parameter-related information, but this is acceptable because there are no parameters to clarify.

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 does not state what the tool actually does. It only says '[UPGRADE REQUERIDO] Esta herramienta requiere un plan superior' (upgrade required, requires a higher plan), which gives no indication that this tool adds a note to an order. The name 'orders_add_note' is the only clue, but the description itself is missing a clear verb+resource statement.

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 tells the user to use 'license_status' to see options, which is a mild pointer to an alternative. However, it provides no guidance on when to use 'orders_add_note' itself or any use cases, prerequisites, or exclusions beyond the upgrade requirement.

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