get_session_pmids

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

No annotations are provided, so the description carries full burden. It does not mention whether the tool is read-only, idempotent, or has any side effects. It focuses on parameters and return format but lacks behavioral traits beyond that.

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 purpose, problem context, argument explanation, return description, and example use. Every sentence adds value, and it is appropriately sized with no redundancy.

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 covers all needed information for using this tool: purpose, when to use, parameter details, expected return (JSON list and search info), and examples. An output schema exists (though not shown), but the description is sufficient for correct invocation.

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 description coverage is 0%, but the description adds significant meaning: it explains the search_index semantics (-1, -2, 0, 1...) and query_filter for filtering, and provides examples. This fully compensates for lack of schema documentation.

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 list of PMIDs stored in the session, solving agent memory overload. It is specific about what resource (session PMIDs) and action (get) it performs. Among siblings, no other tool directly retrieves session PMIDs, so it is well-differentiated.

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 explains when to use this tool: when the agent's memory is full or to avoid storing many PMIDs, and can retrieve from session anytime. However, it does not explicitly state when not to use or provide alternatives among siblings, though none directly compete.

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