make_get_records

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

No annotations provided, so description must shoulder the burden. It discloses the default limit and cap, but does not mention read-only nature, authentication requirements, or any potential side effects. Acceptable but minimal.

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 sentences delivering all essential information. No redundancy. Front-loaded with core purpose.

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, description compensates by describing record structure. Covers purpose, limit behavior, and result shape. Lacks error conditions or pagination details, but adequate for a simple list 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 coverage is 100%. Description adds value beyond schema by explaining the result structure (key and data object) and that limit defaults to 100. This aids parameter understanding.

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 verb 'List' and the resource 'records in a Make.com data store'. It distinguishes from siblings like make_add_record and make_delete_record, providing a specific scope.

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 mentions default cap and max, but lacks explicit guidance on when to use this tool versus alternatives like make_list_data_stores or other sibling tools. No when-to-use or when-not-to-use context.

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