mike_get_values

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

Given no annotations, the description declares read-only behavior and license requirement, but lacks details on error handling, performance, or edge cases. Adequate but not comprehensive.

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 sentences, front-loaded with purpose, no wasted words. Efficiently communicates core information.

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 4-parameter read tool with no output schema, description covers purpose, parameters, read-only nature, and license. Lacks error handling and return format, but sufficient for typical use.

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 coverage is 75%; description adds context for table examples and optional muids, but does not significantly enhance parameter meaning beyond what schema provides. Adequate.

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?

Description clearly states the tool reads parameter values from MIKE+ tables, specifying the resource (e.g., msm_Link) and action (read). It distinguishes from siblings like mike_set_values by implying a read-write pair.

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?

Explicitly states read-only and license requirement. Provides usage advice ('Use this to identify current parameter values') but does not explicitly contrast with write alternatives or state when not to use.

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