olist_info

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

No annotations are present, so the description must carry the full burden. It states that the tool retrieves account information, implying a non-mutating operation, but it does not disclose any additional behavioral traits such as authentication requirements, potential side effects, or response specifics. The description repeats the tool's purpose without adding behavioral context beyond it.

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 concise: two short sentences including the endpoint and documentation link. It wastes no words and is front-loaded with the core purpose.

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?

For a zero-parameter info tool, the description is adequate: it states what it does, identifies the endpoint, and provides a documentation link. However, it does not mention what type of information is returned or any auth context, which could be relevant for a no-annotations tool.

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, and the input schema's properties are empty (100% schema coverage). The description appropriately focuses on the operation itself; parameter details are not needed. Baseline 4 for zero-parameter tools 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 the tool's purpose: 'Obter informações da conta API 2.0' (Get API account information). The verb 'obter' with resource 'informações da conta' is specific, and it distinguishes from sibling tools that target specific entities (contacts, products, orders, etc.).

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?

No guidance is provided on when to use this tool versus alternatives. It only states the endpoint and documentation link, without explaining scenarios or prerequisites. Since there are many sibling tools, explicit context or exclusions would be helpful.

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