create_consult

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

With no annotations, the description must disclose behavioral traits. It states 'open a new clinical consult', implying creation, but does not clarify side effects, required permissions, data persistence, or what exactly 'open' entails. The description is too sparse to provide adequate transparency.

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 very short (7 words), making it concise. However, it sacrifices necessary detail, crossing the line from concise to insufficient. It earns a 4 because it is efficient but lacks completeness.

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 tool has an output schema (undisclosed), a description should indicate what is returned. The description only tells the action, not the result. Additionally, no context about post-creation steps or interactions with sibling tools is provided, leaving the agent underinformed.

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 singular parameter 'consult_json' is a string with no schema description (0% coverage). The description adds zero explanation about its expected format, structure, or content. The agent is left guessing what JSON fields are required or acceptable.

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 uses 'Open a new clinical consult (visit record)', which clearly identifies the verb and resource. It distinguishes from siblings like 'create_animal' by specifying 'clinical consult'. However, 'open' is slightly less direct than 'create', and the purpose is clear but not exceptional.

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?

No guidance is provided on when to use this tool versus alternatives such as 'find_consults' for reading or 'update_animal' for modifications. There is no mention of prerequisites, context, or exclusion criteria.

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