Query Buildin database

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

The description discloses pagination behavior with next_cursor/has_more, which is important for a query tool. No annotations exist, so the description carries the transparency burden and does so adequately.

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?

Two concise sentences that front-load the purpose and key behavior (pagination), with no redundant 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 no output schema and five parameters, the description is basic. It covers core functionality and pagination but omits explanation of start_cursor relative to next_cursor, and lacks details on filter/sort structure.

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?

With only 40% schema description coverage, the description adds no additional parameter details beyond mentioning optional filter and sort. It does not explain the structure of filter or sort objects or the start_cursor/page_size parameters.

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 it queries rows of a Buildin database with optional filter and sort, distinguishing it from sibling tools that create, update, or archive pages.

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 usage for querying database rows but does not explicitly guide when to use this tool over alternatives like buildin_search or buildin_search_and_fetch.

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