Get Temp status

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

Describes read-only nature (checking lifecycle) and credential handling from .tempmd file. Without annotations, it adequately discloses key behavioral traits, though could mention error handling.

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 precise sentences: first lists output details, second covers credential behavior. No redundant 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?

Provides specific return values (status, expiry, restorability) and credential behavior. Lacks output schema but sufficient for a status check. Minor omission of error scenarios.

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?

Adds meaning to project_dir by explaining fallback, but temp_id and update_token lack any description. With only 33% schema coverage, more parameter details would help.

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?

Clearly states the tool checks a Temp's lifecycle status (active/cooling/expired) and whether it can be restored, distinguishing it from siblings like list_temps or restore_temp.

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?

Indicates credential fallback behavior when project_dir is omitted, offering implicit usage guidance. Lacks explicit when-to-use vs. alternatives, but context is clear.

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