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

The description adds the specific behavioral detail '(paginated),' which is crucial mechanical context not provided by the annotations or schema. Since annotations cover the safety profile (readOnlyHint), the description fulfills its role by detailing core operation mechanics.

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?

It is highly concise, using a single sentence to communicate the core function and a key constraint (pagination). There is no waste in the phrasing.

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?

Since no output schema exists, the description could benefit from hinting at the expected structure or attributes of the records being returned. As is, it only defines the action, not the outcome details.

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?

The description mentions 'a collection,' which relates directly to the collection parameter. Since schema coverage is moderate (67%), the description adds marginal value by summarizing the resource type, but does not compensate for the gaps in documentation.

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 action ('Read') and the resource ('records stored in a collection'). It distinguishes itself from mutation tools like create_record or update_record by focusing on 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 does not provide explicit guidance on when this tool should be used versus other siblings. It offers no prerequisites or exclusionary conditions for agent selection.

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