Pedidos de compra (MRP)

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

With no annotations, the description notes the endpoint name and a key behavioral detail: in the DFL environment it returns PEDIDOS. Also warns that the base may be empty. Adequate for a list tool.

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?

Extremely concise—two sentences with no fluff. The purpose is front-loaded, and critical notes are included without wasted words.

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 moderate complexity, no output schema, and involved sibling tools, the description provides enough context to operate correctly. The note about empty data and the endpoint name add completeness.

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?

All 6 parameters are described in the schema (100% coverage). The description adds meaning by explaining that omitting ID returns a list, while providing branchId+code returns a specific record, which complements 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 'Pedidos de compra do MRP' and specifies the endpoint. It distinguishes between listing all (no ID) and retrieving a specific order (with branchId+code). Among sibling tools focused on MRP, this tool is unique.

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?

Provides clear guidance on how to list all versus get a specific record. Lacks explicit when-not or alternatives, but the context is sufficient for correct usage.

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