get_case_status

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

Without annotations, the description carries the full burden. It discloses that the tool reads specific files (CaseStatus log and env_build.xml), implying no side effects. However, it does not mention required permissions, input validation, or any potential performance impact for large cases.

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 sentences, front-loaded with the main purpose. Each sentence adds value: the first states the output, the second clarifies data sources. No wasted words.

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 tool with one parameter, no annotations, and an output schema, the description is adequate but not fully complete. It mentions reading specific files and reporting completed steps, which covers the basic behavior. However, it doesn't describe the output format (though an output schema exists) or what 'full status' entails beyond steps.

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 single required parameter 'case_dir' has no schema description (0% coverage), so the description must compensate. It only implies a directory path is needed without specifying format, path conventions, or whether it must be absolute. The description adds minimal meaning beyond the parameter name.

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 identifies the tool as returning the status of a CESM case, using 'build/run/submit' to specify scope. It distinguishes from sibling tools like 'get_job_status' which likely targets job queues, but could be more precise about what 'full status' means.

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 on when to use this tool versus alternatives. For example, it doesn't explain how it differs from 'get_job_status' or whether it should be called after specific build steps. The context signals show 16 sibling tools, making this gap significant.

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