Does 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 does disclose that the input value is discarded (check-only semantics), which is a useful trait, but it never states what the tool returns (boolean? echo?), whether the 9 other parameters are used at all, or any auth/side-effect profile for a 9-parameter tool.

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?

It is a single front-loaded fragment with zero padding, which is good, but the extreme terseness reads as under-specification rather than economical structure and omits a verb to anchor the phrase.

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 nine parameters, no annotations, and no output schema, the description should explain the validation result and the role (if any) of the other parameters. It covers only the bigint shape concern and leaves the rest of the tool's behavior unexplained.

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 100%, so all nine parameters are documented in the schema itself, giving a baseline of 3. The description adds only 'value discarded', which restates the schema note 'discarded after the shape check' and contributes no further semantic depth.

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 phrase 'unsigned 64-bit decimal shape' identifies the resource being checked and 'value discarded' hints it is a validation-only tool, so the core intent is inferable. However there is no verb (validate/check), and given the tool name 'bigint-ok' plus nine unrelated parameters, the description never states that this is a shape validator returning a pass/fail result, nor distinguishes it from siblings like search-query-len or file-path-ok.

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 when-to-use guidance, no exclusions, and no reference to any alternative sibling tool. The agent is left to infer the context entirely.

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