Produtos (MRP)

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions that the database might be empty, which is useful, but fails to disclose other important aspects such as auth requirements, rate limits, or potential side effects. The basic read behavior is implied but not explicitly stated.

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 concise at two sentences, with no filler. It uses a clear structure: first sentence states the overall purpose, second sentence explains the two modes. It earns a high score for efficiency.

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 6 parameters, no output schema, and no annotations, the description should provide more context. It does not describe the return format, pagination behavior, or what fields are available. The note about an empty database is helpful, but overall the agent is left with gaps in understanding the full tool behavior.

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?

Since schema coverage is 100% and all parameters are documented in the schema, the description does not need to add much. It does note that branchId and product are used together for a specific product, which aligns with the schema but adds no new semantics beyond what is already in the property descriptions.

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 consults MRP products and specifies the two modes (list all vs. single product), making the purpose unmistakable. However, it does not differentiate from sibling tools like protheus_saldo_estoque_mrp, which also deal with MRP data.

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 explains when to use the tool with or without parameters, but it does not provide guidance on when not to use it or mention alternative tools for similar queries. This leaves the agent without exclusion criteria.

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