olist_pdv_pedido_obter

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. The verb 'Obter' implies a read operation, but it does not specify return format, potential errors, authentication requirements, or any side effects. The documentation link is not a substitute for inline disclosure.

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 concise: a single sentence plus a documentation URL. It is front-loaded with the purpose and endpoint, and the URL may provide additional reference. No unnecessary wording, though it could be slightly more informative without losing conciseness.

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?

Despite being a simple tool with one parameter and no output schema, the description does not explain what the response contains or how it differs from other order retrieval tools. The documentation link could fill gaps, but the description itself is not complete enough for an agent to confidently invoke the tool without external resources.

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 input schema has one parameter 'id' with a description, giving 100% coverage. The tool description adds no additional meaning about the parameter beyond what the schema already provides, so the baseline of 3 applies.

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 'Obter Pedido' (Get Order) with the 'PDV' prefix, indicating it retrieves a PDV (point-of-sale) order. This distinguishes it from sibling tools like 'olist_pedido_obter' which handles regular orders. The endpoint name 'pdv.pedido.obter' reinforces the specific resource.

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 provides no guidance on when to use this tool versus alternatives. It only mentions the endpoint and a documentation link. There is no mention of prerequisites, whether this is for single order retrieval by ID, or when to prefer other order-related tools.

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