probe_list_query

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

The description discloses that the tool is read-only ('GET-only') and imposes a page size cap, which are key behavioral traits. However, with no annotations, it fails to mention other important behaviors like error handling, rate limits, or whether the query can return all results or just a sample. This leaves gaps for the agent.

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 at one sentence, but it sacrifices clarity. While there is no wasted text, it omits crucial details that would fit within a few more phrases. The structure is front-loaded with key info but overall too terse for a tool with 4 parameters.

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 having an output schema, the description does not mention what the output contains or how pagination works beyond a capped page size. It also lacks information on error conditions, data freshness, or relationship to other tools. This incompleteness hampers autonomous selection and invocation.

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 0%, so the description bears full responsibility for explaining parameters, but it only vaguely implies that 'entity' is the target and 'page_size' is capped. It offers no explanation for 'filters' or 'properties', requiring the agent to rely on parameter names 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 clearly specifies the tool's action ('Probe a bounded list query against production') and includes key distinguishing traits ('GET-only, capped page size'). This differentiates it from sibling tools like probe_entity_sample or execute_read_plan, which focus on different aspects of reading 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?

No guidance is provided on when to use this tool versus its siblings. There are no explicit instructions on prerequisites, context, or alternatives such as probe_entity_sample or plan_cross_entity_read. The agent must infer usage solely from the sparse description.

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