retrieve_state

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral context beyond 'by ID' (already in the name), but it is consistent with annotations. No extra details about return format or error behavior are provided, but the annotations carry the burden adequately.

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 a single, front-loaded sentence with no filler words. It efficiently states the tool's core function, and the brevity is appropriate for a simple retrieval operation.

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?

Despite the simplicity, the description is incomplete: it fails to explain the required project_id parameter, and without an output schema the agent has no indication of what the response contains. The description relies heavily on the tool's name and sibling context, which is not sufficient for full understanding.

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 has two parameters with no descriptions (0% coverage), so the description must clarify their roles. It only mentions 'by ID,' which likely refers to state_id, but entirely ignores project_id, leaving the agent unclear about the purpose of the second required parameter and how the two IDs relate.

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 uses specific verb 'Retrieve' with resource 'state' and scope 'by ID', clearly distinguishing it from sibling retrieve_* tools (e.g., retrieve_project) and from list_states. The purpose is unambiguous.

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?

While the description implies this tool is for fetching a single state by its identifier, it offers no explicit guidance on when to use it versus list_states or other retrieve tools, nor does it mention any prerequisites. The usage is implied by the name and standard retrieve semantics.

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