Get session report

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate that. It adds useful context by listing the detailed contents of the report, which goes beyond the schema. However, it doesn't disclose any potential performance costs or whether the report is generated on demand, but it's a read-only operation so the burden is lower.

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, dense sentence that lists all the report contents without fluff. It is slightly long but packs useful detail, making it efficient. The key content list is front-loaded after 'Session report'. Every word contributes to explaining what the tool delivers.

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 complexity—it returns a rich report with many fields—the description enumerates all the key sections. The output schema exists and likely details the exact structure, so the description doesn't need to repeat that. The only minor gap is that it doesn't mention how to obtain the sessionId beyond the schema's pointer to start_session, but that's already covered.

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 only parameter is sessionId, and its schema description ('Session handle returned by start_session.') fully explains its semantics. The description adds no additional information about the parameter, but with 100% schema coverage, the baseline 3 is appropriate.

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 purpose as fetching a session report and enumerates the specific content it includes (outcome, budget usage, completed work, etc.). It distinguishes it from tools like get_session, which likely returns basic session info, though it doesn't explicitly name a sibling for contrast.

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 implies that this should be used after a session has been started and when a detailed report is needed, but it does not explicitly state when to use it vs. alternatives like get_session or list_sessions. No guidance on when not to use it is provided.

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