telys_ids

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

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds substantial behavioral detail beyond that: no pagination, full id list in a single response, unspecified internal row order, client-side sorting advice, and explicit failure conditions for missing collections or multi-key where filters.

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 dense but efficient: purpose, sibling differentiation, parameter guidance, result shape, ordering caveat, and failure modes are all covered in a compact, front-loaded structure. No sentence is wasted.

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?

For a two-parameter read-only enumeration tool with no output schema, the description covers everything an agent needs: what is returned, pagination behavior, ordering semantics, and failure conditions. The safety profile is already carried by annotations, and the description fills the remaining operational gaps.

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 description coverage is 100%, so the schema already documents both parameters. The description restates the single-key equality constraint and gives an example, but it does not add significant meaning beyond what the schema's maxProperties and descriptions already provide.

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 opens with a specific verb and resource: 'Return the live (non-tombstoned) external ids in a collection.' It also distinguishes itself from siblings by explicitly stating this is 'enumeration without ranking,' which separates it clearly from telys_search and telys_count.

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 names the relevant siblings and their behaviors: 'telys_search returns ranked hits with scores for a query; telys_count returns just the cardinality.' This gives an agent explicit context for choosing this tool over alternatives, and the required/optional parameter breakdown reinforces when it applies.

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