get_malignant_conditions

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description only needs to add behavioral context. It adds ontology-wide scope, but does not describe list contents, pagination, or any caveats about the returned data. This is adequate but not rich.

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, front-loaded with the core operation. The second sentence is slightly redundant by restating 'malignant skin conditions' as 'skin cancers,' so it is concise but not maximally tight.

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 parameterless read-only list tool, the description states what it returns and its purpose, and the lack of an output schema is mitigated by the simple list semantics. It could be slightly more complete by noting what fields or format the returned list contains.

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 tool has zero parameters, so the input schema is fully documentative and no parameter explanations are needed. The description appropriately adds no parameter-specific details; the parameterless baseline of 4 applies.

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 identifies a specific verb ('Get'), resource ('list of all malignant skin conditions'), and scope ('in the ontology'). It is distinguishable from sibling concept-search tools by emphasizing 'all malignant skin conditions,' though it does not explicitly name a sibling it is not.

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 advises 'Use for educational purposes about skin cancers,' which gives an intended context but no when-not-to-use guidance and no comparison with alternatives such as lookup_medical_concept or search_medical_concepts. The usage guidance is present but not robust.

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