Query any BC API entity (read-only)

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

The description explicitly labels the tool as read-only and shows a GET pattern, which is transparent about its safe operation. However, it does not mention potential response size limits, pagination, or error behavior, though these are less critical for a read-only escape hatch.

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 and front-loaded: it opens with the purpose, then scope, then custom API usage, then a clarifying example. Every sentence contributes meaningful information without redundancy.

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 generic nature and lack of output schema/annotations, the description covers the essential aspects: what it does, when to use it, and how to use it with concrete examples. Minor gaps exist around response format and pagination, but these are not critical for an escape hatch.

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 practical value by showing the combination of path and params with a real OData filter example, plus explaining how api_route is used for custom APIs. This goes beyond the schema alone.

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 states 'Read-only escape hatch: GET any Business Central API entity set or record', providing a specific verb and resource. It distinguishes itself from sibling tools by explicitly covering entities not exposed as dedicated tools and custom APIs via api_route.

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?

It clearly states it covers 'standard v2.0 entities not exposed as dedicated tools' and custom APIs via api_route. This implies use when no dedicated tool exists, and the example provides a concrete pattern for invoking it.

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