whodb_platform_ontology_fast_lookups

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 without the description. The only added behavioral note — workspace targeting applies to this call without changing session defaults — largely restates the schema's own workspace description, and nothing is said about result volume or pagination.

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?

Two short sentences, no filler, with the core purpose front-loaded before the workspace caveat. Every clause carries information.

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 read-only list tool with full schema coverage and no output schema, the description plus schema covers what an agent needs to invoke it. It could say more about what a fast lookup record contains or whether results are bounded, but nothing required for correct invocation 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 description coverage is 100%, so the baseline is 3. The description adds the useful framing that 'id' scopes to one ontology object type, but it does not clarify the id format or expand on 'fields' beyond the schema's own guidance, and the workspace sentence mirrors the schema verbatim.

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 and resource ('List saved fast lookups') plus the scoping unit ('one ontology object type'), which separates it from the create/delete fast-lookup siblings by verb alone. It stops short of explicitly contrasting itself with whodb_platform_ontology_fast_lookup_suggestions or the create/delete pair, so it is clear but not sibling-differentiating.

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 verb 'List' implies read usage and the workspace sentence hints at per-call targeting, but there is no explicit when-to-use guidance, no mention of when to reach for fast_lookup_suggestions or create_ontology_fast_lookup instead, and no stated prerequisites (e.g. the object type must already exist). Usage is implied rather than directed.

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