telys_ids

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds behavioral detail: tombstoned entries are excluded ('live (non-tombstoned)'), and it discloses two failure modes (collection missing, where with more than one key). This adds useful context without contradicting annotations.

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 three dense sentences: purpose, use case, and requirements/failure conditions. Every sentence earns its place, with no redundant filler, and the core action is front-loaded.

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 simple two-parameter read-only enumeration tool with no output schema, the description covers purpose, usage, requirements, and failure modes. It could mention the return format (e.g., array of ids) or any pagination, but the stated purpose and annotations make the behavior clear enough for correct invocation.

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 only 50% ('where' has a description, 'collection' does not). The description compensates by explicitly stating collection is required, giving an example for where (scope=project:acme), and reiterating the one-key constraint. This adds meaning beyond the bare schema fields.

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 'Return the live (non-tombstoned) external ids in a collection', which is a specific verb+resource statement. It further clarifies the tool's role as 'enumerate what is stored before a bulk update or delete', distinguishing it from search, get, and count siblings without needing to name them.

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 explicitly states a concrete use case: 'Use to enumerate what is stored before a bulk update or delete.' It also provides parameter requirements and failure conditions, but does not explicitly compare to alternatives like telys_search or telys_get, so it stops short of full when-not guidance.

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