Descubrir mi sucursal

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

Without annotations, the description carries the full burden. It explains the two-step process (returning a snippet, then validating the result), the snippet's return format, and that the result must be passed back. No destructive actions are mentioned, which is appropriate for a read operation.

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 a single paragraph of about three sentences, efficiently covering the tool's purpose and mechanics. It could be more structured (e.g., separate usage notes), but it is concise and front-loaded.

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 (browser interaction, validation step), the description covers key aspects: getting the snippet, executing it, and passing back the result. No output schema exists, but the return format is described. It is sufficiently complete for correct agent usage.

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 coverage is 100%, and the description adds context: 'store' specifies the Cencosud chain (jumbo/santaisabel), and 'discovered' is the result of the browser snippet. The explanation of the flow enriches parameter understanding beyond 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 tool obtains the branch code (branchId) from the browser, avoiding the need to ask the user. It specifies the output (browserSnippet) and distinguishes itself from other tools that don't perform browser interaction.

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 implies using this tool when the branchId is needed and a browser snippet can be executed. It does not explicitly state when not to use it or name alternatives, but the context makes the usage clear.

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