classify_lesion_features

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

No annotations are provided, so the description carries the behavioral disclosure burden. It states that the tool returns possible conditions, risk level, and recommendations, which is meaningful, but it does not mention limitations, whether it is advisory-only, or how it behaves with missing inputs. For a classification tool with medical implications, more caveats would be helpful.

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 only three sentences, with no filler. It opens with the main action, then states the output, and ends with a usage hint, all efficiently.

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?

The tool has no output schema and no annotations, so the description is responsible for explaining the outcome; it does name outputs. However, a medical risk classifier arguably should provide more context about how authoritative or complete the classifications are, and possible conditions/recommendations are not further described.

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 parameters are already individually documented. The description's mention of 'ABCDE features' maps to the schema, but it adds no parameter-specific detail beyond the schema, earning the baseline.

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 clearly specifies a verb ('Classify') and a resource ('a lesion based on its ABCDE features'), and it states the output: possible conditions, risk level, and recommendations. It is distinct enough from siblings like get_mole_analysis, but it does not explicitly call out a sibling to distinguish itself.

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 sentence 'Use this to help interpret mole analysis results' gives useful context for when the tool applies, but it does not compare with alternatives or explain when not to use it. With several related medical tools nearby, explicit routing guidance would improve the description.

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