Retrieve a read-only session manifest that groups processes and separates observed, static-candidate, and unresolved evidence for debugging C/C++ fault artifacts.
Return a read-only session manifest with separate evidence classes.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| names | Yes |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses only that the operation is read-only; it does not describe pagination behavior, required inputs, evidence-class semantics, or response characteristics.
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 front-loaded sentence with no wasted words. However, it is under-specified for a tool with required parameters and ambiguous evidence-class behavior, so its brevity is not fully effective.
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?
With no annotations, no output schema, zero parameter-description coverage, an unexplained required 'names' argument, and many similar sibling tools, the description is far too incomplete to guide 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?
The schema has 0% description coverage for two parameters, 'names' and 'page', and the description does not mention either parameter or how they should be used. No compensation is provided for the missing 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 states a specific verb and resource: return a read-only session manifest. However, 'separate evidence classes' is vague and does not distinguish this tool from siblings such as get_session, list_sessions, or get_evidence_summary.
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?
There is no guidance on when to use this tool versus the many sibling tools that also retrieve session or evidence data. No conditions, exclusions, or alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.