get_session_summary

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

No annotations are provided, so the description must disclose behavior. It states the tool returns summary data without indicating side effects or permissions. While it explains parameters and examples, it lacks explicit confirmation that the tool is read-only, error conditions, or rate limits, which are expected for a data retrieval tool.

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 purpose statement, Args, Returns, and Examples. It is slightly redundant (purpose and Returns overlap), but the front-loaded key information and clear sections make it easy to parse.

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 low complexity (2 optional parameters) and the presence of an output schema, the description adequately covers parameters, return values, and usage examples. It provides enough context for an agent to correctly invoke the tool without missing critical details.

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 description's Args section adds significant meaning beyond the input schema: it explains that include_history controls inclusion of full history, history_limit only applies when include_history is True, and provides defaults. This compensates fully for the 0% schema description coverage.

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 retrieves a summary of the current session, including cache status and search history, to help the agent understand available data. It distinguishes the tool from siblings like get_session_log or get_session_pmids by focusing on a concise summary rather than raw logs or 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 implies usage for understanding session state with examples showing typical calls. However, it does not explicitly specify when not to use this tool or mention alternatives like get_session_log for detailed history, leaving some room for ambiguity.

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