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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the dual-mode behavior (single vs list), which is useful context, but says nothing about defaults, clamping (limit), pagination interaction, or result shape.

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 zero waste that captures both usage modes. Nothing is padded or redundant.

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 6-parameter query tool with a nested MongoDB-style query object and no output schema, the description covers the id-vs-query decision but leaves sort, skip, limit, and fields behavior to the schema. Adequate but thin given the tool's complexity.

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 high (83%), so most parameters are documented in the schema itself, making 3 the baseline. The description only reinforces the id/query distinction, adding marginal meaning beyond what the schema already states.

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 clear verb ('Find') and resource ('LimPartner records'), and distinguishes its two modes: single-record by id vs filtered list by query. It does not explicitly differentiate from the ~50 sibling query_lim* tools, but the resource name is the natural discriminator in this family.

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?

It gives mode-selection guidance within the tool ('pass id for one record, or query for a filtered list'), which tells the agent how to choose between the id and query paths. However, it offers no guidance on when to prefer this resource over the many sibling query tools, nor any prerequisites.

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