whodb_platform_datasets

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful non-annotation context: that the workspace argument targets a single call 'without changing defaults', which clarifies session-state behavior an agent cannot read off the 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?

Three short sentences, front-loaded with the core action, then filters, then the targeting mechanism. No filler and nothing buried.

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 read-only list tool with no output schema, the description names the resource, the scoping, the useful filters, and the override mechanism, while annotations carry the safety profile and the schema carries every parameter. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so the schema itself documents all ten parameters including the nested workspace object. The description only echoes the name/schema_mode filters and the workspace shape, adding no syntax, default, or pagination nuance beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb ('List') and resource ('datasets') scoped to the 'selected hosted project', which an agent can parse immediately. However, it does not distinguish this list tool from the singular sibling whodb_platform_dataset or from whodb_platform_dataset_rows, so an agent must infer the difference from the name alone.

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?

'Use name and schema_mode filters when known' gives a light hint about when filters are worth attaching, and the workspace sentence explains per-call targeting. But there is no when-not guidance, no mention of alternatives like the singular dataset tool, and no statement of prerequisites (e.g. a selected project must exist).

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