get_session

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

With no annotations, the description carries the transparency burden. It adds useful context by listing the possible status_enum values (working, blocked, etc.) and clarifies the kind of data returned. It doesn't discuss failure modes or permissions, but for a simple read operation this is reasonably transparent.

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 well-structured with a clear opening sentence, usage guidance, an Args section, and a Returns section. Every sentence provides useful information without redundancy, making it appropriately sized and scannable.

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?

The description is complete for a simple retrieval tool: it specifies the input, output, and interprets the key status field. It could mention what happens for invalid session_ids or explicitly differentiate from list_sessions, but given the output schema exists and the tool is straightforward, it covers the essential context.

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 schema only says 'session_id' is a string with no description. The tool description compensates with 'The identifier of the session to retrieve,' which adds clear meaning. Even though schema coverage is 0%, the description fully explains the parameter's purpose.

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 tool's function: 'Retrieve details about an existing Devin session.' It uses a specific verb and resource, and distinguishes from siblings like list_sessions (which lists) and resume_session (which resumes) by focusing on retrieving a single session's details.

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?

It explains when to use the tool: 'Use this to inspect the current status, messages, and metadata of a session' and gives concrete scenarios like checking if a session is running or sleeping. While it doesn't explicitly mention alternatives or exclusions, the context is clear enough for an agent to select it appropriately.

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