get_metadata

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

The description labels the tool as a read operation ('Get'), implying no destructive side effects. Since annotations are absent, this is sufficient. However, it lacks further details like what metadata is returned or any security considerations.

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 two sentences long, wastes no words, and front-loads the core action. Every sentence serves a clear purpose.

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 tool's simplicity (one parameter, no output schema, no annotations), the description covers the basic purpose and a prerequisite. However, it omits details about the return value (what metadata is included), which is important for an agent to understand the tool's output.

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?

With 0% schema coverage, the description fails to add meaning to the session_id parameter beyond restating its name. The prerequisite mentions it's created via create_session, but the parameter's format, source, or validation rules are not explained, leaving the agent to infer.

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 it retrieves metadata for an existing PTY session, specifying the verb 'Get' and the resource. While it distinguishes itself from sibling tools like send_text or snapshot, it does not explicitly differentiate from other read-oriented siblings like transcript or snapshot_screen.

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 provides a prerequisite (existing session via create_session), which is helpful guidance. However, it does not offer any context on when to use this tool versus alternatives, such as when to choose get_metadata over snapshot_screen or transcript for reading session data.

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