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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds useful substance by naming the returned content (connection card, auto-fill flag, expiry), which matters because there is no output schema. It doesn't mention error behavior for a stale/ended session.

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?

One sentence, front-loaded with the operation and scoped by id, with the key return fields appended. 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 simple read-only getter with full schema coverage and no output schema, the description covers the essentials and previews return content. Slightly incomplete in not distinguishing itself from closely named session-related siblings.

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 coverage is 100% and there is a single well-described uuid parameter, so the baseline is 3. The description only adds 'by id', which the schema already conveys, adding no new semantics.

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?

States a specific verb and resource ('Re-fetch a sandbox session's connection card by id') and even names what the payload contains. It does not explicitly differentiate itself from siblings like sandbox_get_status or fixsim_get_session, so it stops short of a 5.

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?

'Re-fetch' plus the schema's 'Session id from sandbox_create_session' implies this is used after creating a session to refresh its state. However, it never says when to prefer this over sandbox_get_status or sandbox_get_messages, and states no exclusions, so guidance is only implied.

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