retrieve_state

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

The description states that it returns a 'State object', but the exact structure is likely defined in the output schema. The annotations already indicate readOnlyHint and openWorldHint, so the description adds minimal behavioral context. No contradictions with annotations.

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 remarkably concise, consisting of a single line of purpose and a brief parameter list. Every element is necessary and front-loaded; there is no superfluous content.

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 presence of an output schema, the description appropriately does not elaborate on return values. It sufficiently covers the two required parameters. For a simple retrieval tool with low parameter count, the description is complete enough, though it could mention that the state must exist or handle errors.

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 input schema has 0% description coverage, but the description explicitly adds semantics by noting that 'project_id' is a 'UUID of the project' and 'state_id' is a 'UUID of the state', providing essential context beyond the schema's type definitions.

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 states the action ('Retrieve'), the resource ('state'), and the identifying parameters ('by ID'). It distinguishes from siblings like 'list_states' and 'create_state' by specifying retrieval of a single state via IDs.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It implies usage for fetching a specific state, but lacks comparison with 'list_states' or 'retrieve_state_by_identifier' (not present, but siblings include other retrieve tools). This is adequate but not exemplary.

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