tdm_get_session_state

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states that hints and status are provided, but does not specify whether the operation is read-only, what side effects exist, or the exact format of the output. The description is too vague about the actual behavior.

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 sentence that front-loads the core purpose. It is concise and avoids unnecessary words, though the phrasing 'local TDM balance snapshot hints' is slightly complex but still clear.

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 no output schema, the description should explain what the tool returns. It mentions 'balance snapshot hints and wallet status' but does not detail the format or structure of the output, leaving gaps for the agent. The tool simplicity partially compensates, but more specificity is needed.

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 tool has zero parameters, and the input schema has 100% documentation coverage (empty). The description does not need to add parameter details, and it provides sufficient context for a parameterless tool.

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 that the tool provides balance snapshot hints and wallet status to determine whether x402 execution should continue or alternative tools should be used. It names the specific resources and implies the decision-making purpose, but could be more direct about it being a 'get state' operation.

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 explicitly suggests when to use this tool (before deciding on x402 execution) and mentions alternative tools (tdm connect, tdm fuel, tdm sweep). It lacks explicit 'when not to use' guidance, but the context is clear.

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