get-collection

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only says 'Get' and gives examples, without mentioning pagination, permissions, rate limits, or error behavior. This is minimal beyond the basic operation and leaves the agent without important expectations.

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 two sentences long, front-loaded with the core action, and provides a helpful instruction without any filler. Every word earns its place.

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?

The description covers the tool's main purpose and prerequisite, but with no output schema it fails to describe the return format, pagination, or limit behavior. This is a clear gap for a tool that fetches data, but the core usage is still adequately conveyed for a relatively simple getter.

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 adds meaning beyond the schema by giving example selector values ('MedicalRecords', 'Liens') and explicitly directing users to the discover-schema tool for valid selectors. The case_id parameter is already described in the schema, and the limit parameter has range constraints, so the description compensates for the partial schema coverage.

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 starts with the specific verb 'Get' and identifies the resource as 'custom collection data' with concrete examples (medical records, liens, settlements). This clearly distinguishes it from sibling tools like get-case or list-documents, which operate on different 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?

It gives an explicit prerequisite: 'Use discover-schema first to find available selectors.' This tells the agent what to do before invoking the tool. It does not spell out when not to use it, but the focused 'custom collection' language provides a clear usage context.

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