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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Free' (a cost attribute) and instructs to pass a token, but it does not state that the operation is read-only, has no side effects, or what happens on invalid tokens. The behavioral profile is largely undisclosed.

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 very short but not well-structured. The standalone 'Free.' adds little value and the phrase '/shelf/shelf-pass-100' is cryptic. It is under-specified rather than efficiently concise, and the main purpose is not 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?

With no output schema and no annotations, the description should explain enough to invoke the tool correctly. It provides the token source but omits the return value, error behavior, and confirmation that the operation is safe. For a simple one-parameter tool this is still a notable gap, though the title partially covers the expected result.

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 already describes the token as a 'pass_… token' with 100% coverage, so the baseline is 3. The description adds the source of the token ('from buy_shelf_pass /shelf/shelf-pass-100'), which is helpful context. However, the endpoint path is cryptic and the instruction is terse, adding limited meaning beyond the schema.

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 does not explicitly state that the tool checks a credit balance. It only says 'Free. Pass the token from buy_shelf_pass /shelf/shelf-pass-100.' This is an instruction, not a clear statement of the operation. The title provides the purpose, but the description itself fails to describe what the tool does.

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 gives a prerequisite (obtain token from buy_shelf_pass) but does not indicate when to use this tool versus its siblings. It does not mention alternative tools like check_broker_authority or check_carrier_authority, nor does it specify conditions or exclusions. The token-source hint is useful but not enough for selection decisions.

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