CPI Query (read any entity set)

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

No annotations are provided, so the description must disclose behaviors. It describes the tool as a read query (non-destructive) and mentions standard OData options, but fails to discuss rate limits, maximum result size (though top parameter suggests 1000), error handling, or any side effects.

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—one sentence plus an example. Every word serves a purpose, and the example immediately clarifies usage. No superfluous information.

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 7 parameters, no output schema, and no annotations, the description gives a clear purpose and example. However, it lacks details on return format, pagination behavior, and potential errors, which are important for a query 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?

Schema description coverage is 57%, and the description adds value by providing an example of using entitySet, filter, and orderby. However, for parameters like top, skip, expand, select, orderby, the schema already provides basic descriptions; the description doesn't add further semantic detail.

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 performs a read query against any CPI OData entity set, with a specific example. This distinguishes it from siblings like cpi_write (write operations) and cpi_get_entity (likely single entity retrieval).

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 implies the tool is for read queries via 'Run a read query', but does not explicitly state when to use it over alternatives like cpi_get_entity or cpi_write. No guidance on when not to use or prerequisites is provided.

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