Get XGR Session Start schema

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

No annotations are provided, so the description carries the burden. It explicitly states that the tool retrieves a schema and enumerates the fields returned (stepId, payload, maxTotalGas). This sufficiently discloses the output structure, though it does not mention any side effects or limitations, which are minimal for a read-only schema retrieval.

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 extremely concise: two sentences that efficiently convey the purpose and a usage caveat. Every sentence adds value, and the key information is front-loaded.

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 has no input parameters and no output schema, the description fully covers the essential context. It specifies the exact schema name and fields returned, making the agent fully informed about the output without needing additional documentation.

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 input schema has zero parameters, so there is no need for parameter explanation. The description does not add parameter info, but the baseline for 0 parameters is 4, and no further value is required.

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 the canonical Workbench Session Start Handoff schema 'xgr-session-start@1' with specific field details (type, stepId, payload, maxTotalGas). It distinctly identifies the resource and differentiates from sibling tools that might deal with other schemas or handoffs.

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 clear when-to-use: for retrieving the Workbench Session Start schema. It also gives a negative instruction ('Do not use entryStepId'), which helps avoid misuse. However, it does not explicitly compare or contrast with similar sibling tools like get_xdala_session_start_handoff.

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