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

The readOnlyHint annotation already covers safety; the description repeats 'Read-only' and adds content categories but discloses no further behavioral traits such as data freshness, response shape, or limitations. This is consistent with the annotations but adds only modest behavioral context.

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, scannable sentence with a front-loaded subject and a compact list of content areas. There is no filler or unnecessary repetition beyond the harmless 'Read-only' suffix.

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?

For a zero-parameter, read-only fact retrieval tool, the description gives a solid inventory of what information can be obtained. It does not describe output format, but no output schema exists; the main gap is the boundary with the proposal-request sibling tools.

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?

There are zero parameters, so schema coverage is effectively complete. The description does not need to explain parameters, and the baseline for a zero-parameter tool is a 4.

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 identifies the tool as a fact sheet about Kratons, enumerating legal identity, address, contacts, countries, languages, services, pricing, and proposal process. It is specific about the resource, though it does not explicitly differentiate itself from closely named siblings like how_to_request_a_proposal.

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 no guidance on when to use this tool versus alternatives. The inclusion of 'how to request a proposal' in the fact list creates potential overlap with the sibling tool how_to_request_a_proposal, but there is no explicit 'use this when' or 'use that instead' guidance.

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