Get Table Data

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves data but does not disclose behavioral traits such as performance implications, error handling, support for joins, or whether tableName must exist. The description is too minimal for a data retrieval tool.

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 a single sentence that is concise and front-loaded with the core action. Every word is necessary and no extraneous content. Ideal for quick understanding.

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 absence of an output schema, the description should at least indicate what the return data looks like (e.g., row format, fields). It does not. Also, with 5 parameters and potential complexity (e.g., WHERE clause syntax), the description lacks completeness. More context on table name validity or query limitations is needed.

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%, so the baseline is 3. The description adds no extra meaning beyond the schema; it merely reiterates 'optional filtering, pagination, and ordering' which directly maps to the 'where', 'first', 'skip', and 'orderBy' parameters. No additional semantics provided.

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 'retrieves data from a specific table' with optional filtering, pagination, and ordering. This distinguishes it from sibling tools like 'execute-query' (custom SQL) and 'describe-table' (metadata).

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 data retrieval with optional filters but provides no guidance on when to use this tool versus alternatives like 'execute-query' or 'describe-batch-tables'. No explicit when-not-to-use or prerequisites mentioned.

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