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

The readOnlyHint annotation already declares this as a safe read operation. The description adds one behavioral fact—that it can return either a single record or a list—but says nothing about default limits, pagination, sorting behavior, or return shape, all of which affect invocation.

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?

A single, front-loaded sentence with no wasted words. It efficiently conveys purpose and the two main usage paths.

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 six parameters, a nested query object, and no output schema, the description is minimal. It does not describe the return format, default limit behavior, or what happens when no id or query is supplied, though much parameter detail is covered in the schema.

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 coverage is 83%, so the baseline is 3. The description goes beyond the schema by explicitly linking 'id' to fetching one record and 'query' to retrieving a filtered list, clarifying the two primary parameters' roles.

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?

States a specific verb and resource: 'Find LimSite records'. It also distinguishes the two retrieval modes (single record via id vs. filtered list via query), making it clear how this tool differs from sibling query_lim* tools that target other resources.

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?

Explicitly tells when to use each mode: 'pass id for one record, or query for a filtered list.' It lacks when-not guidance or named alternatives, but there is no sibling tool for the same resource, so the primary usage decision is covered.

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