whodb_platform_create_ontology_fast_lookup

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false. The description adds important workflow context: a confirmation token is returned and the confirm tool should only be called after user approval. This is valuable beyond annotations, though it doesn't detail what gets destroyed or rate limits.

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 concise with three sentences, front-loading the main action. It is efficient, though the phrase 'for one hosted ontology' could be tightened.

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?

Given the mutation nature, no output schema, and full schema descriptions, the description provides necessary workflow context about confirmation. It is nearly complete, missing only explicit permission requirements or side effects of creating a fast lookup.

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 parameters are fully documented in the schema. The description mentions 'Pass ontology property names in fields' and explains workspace targeting, but it does not add syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Create a fast lookup for one hosted ontology.' It is clear what the tool does, though it does not differentiate from sibling tools like create_ontology_fast_lookup vs other lookup-related tools beyond the 'fast' qualifier.

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 gives clear usage context: default mode returns a confirmation token, do not call confirm until user approves preview. It also explains workspace targeting. However, it does not explicitly state when to use this vs alternatives like delete_ontology_fast_lookup or other creation tools.

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