get_credible_sets

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

Annotations already declare readOnlyHint=true, so no need for that disclosure. However, the description adds little beyond the generic 'flexible filtering options'. It does not disclose behavior such as pagination, how filters combine, or what kind of results are returned. Given the low bar set by annotations, the description still fails to add substantive behavioral context.

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 short and front-loaded, but it is under-specified. A one-sentence overview that omits essential details is not concise in a useful sense; it is merely brief. The structure does not convey enough information to guide invocation.

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?

Despite having an output schema, the tool has 8 optional parameters and multiple sibling tools with overlapping purposes. The description gives no context on how to use the filtering parameters, what 'fields' means, or how pagination works. This is far from complete for a tool of this complexity.

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 0%, so the description must compensate by explaining parameter meanings. It does not mention any of the eight parameters (fields, regions, page_size, study_ids, etc.) or how they interact. The phrase 'flexible filtering options' is a placeholder that adds no specific meaning beyond what the schema already shows.

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 uses the verb 'Query' and names the resource 'credible sets', which is clear enough, but it does not specify the scope (e.g., all credible sets or filtered across studies/variants) nor does it differentiate from siblings like get_study_credible_sets or get_variant_credible_sets. The phrase 'flexible filtering options' is vague and doesn't clarify what kind of filtering is supported.

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?

There is no guidance on when to use this tool versus its alternatives. Sibling tools such as get_credible_set_by_id, get_study_credible_sets, and get_variant_credible_sets suggest distinct use cases, but the description does not mention any of them or provide exclusion criteria. This leaves the agent without clues for tool selection.

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