stemlab_models

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

Beyond the annotations, the description discloses that the call is asynchronous and returns a retained background job, that the base effect flags are 'none', and that inference/download effects are conditional and must be checked via danceflow_component. That is real behavioral context the annotations do not convey, though the tension between 'Base effect flags: none' and readOnlyHint=false is left unexplained.

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 front-loaded sentences with no filler, purpose first and operational follow-ups after. It is slightly telegraphic ('Base effect flags: none.') for an agent that has to interpret what that means against readOnlyHint=false, but the structure is clean.

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?

An output schema exists, so return values need no coverage, and the async/polling behavior is stated. Still, for a non-read-only tool with conditional effects and a nested permissions object, the description does not clarify why it is not read-only or what the inspect result actually enumerates relative to its model-named siblings.

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?

With 50% schema description coverage, the description partially compensates by explaining that effect flags are 'none' at base and that inference/download effects are conditional, which maps onto the permissions object. The nested `arguments` object is empty and gets no explanation of what arguments should be supplied, leaving the required parameter undocumented in both places.

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 gives a verb ('Inspect') and a resource ('StemLab runtime or registered analysis capabilities'), but never uses the tool's own key noun, 'models'. With siblings like stemlab_midi_models and stemlab_evidence_models in the same family, an agent cannot tell from this text whether 'capabilities' means models, runtimes, or something else.

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 useful negative scope ('without starting inference') and routes to danceflow_component for conditional inference/download effects, plus tells the agent to poll danceflow_job_status afterwards. However it never says when to pick this over the model-listing siblings (stemlab_midi_models, stemlab_evidence_models) or danceflow_capabilities, so selection remains partly guesswork.

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