list_studies

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

With no annotations supplied, the description carries the full burden, and it does disclose a real behavioral trait: results are limited to operator-provisioned studies and sealed cases are never touched, which implies an access/permission boundary worth knowing. It says nothing about pagination, ordering, or what happens when the limit is exhausted, leaving the mutation-free read profile only implied.

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?

One short sentence, front-loaded with the action, with no filler or redundant restatement of the name. It is efficient, though the compressed phrasing ('operator-provisioned') costs a little immediate legibility.

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?

An output schema exists, so return values need not be described, and the exclusion of sealed cases is stated. However, for a listing tool with a limit parameter, the absence of any paging or result-set-size guidance leaves the definition only minimally complete.

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 single 'limit' parameter has 0% schema description coverage, and the description never mentions it, so its meaning (page size? cap?) and the default of 20 are undocumented anywhere. With coverage this low, the definition should compensate and does not.

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 names a concrete action and resource ('Find ... studies') and narrows scope to 'operator-provisioned' while excluding 'sealed cases', which meaningfully separates it from lookups like get_study or get_study_cases. It stops short of 5 because 'Find' is left ambiguous about whether this is a paginated enumeration or a search, and no sibling is named explicitly.

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 explicit when-to-use or when-not-to-use guidance against alternatives such as get_study (single study) or list_study_attempts. The 'without accessing sealed cases' clause is a scope constraint on results rather than a routing rule, so an agent must infer that this is the discovery/enumeration entry point.

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