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

readOnlyHint=true already declares the safety profile, so the description only needs to add context. It does add the REST endpoint (GET /rest/opportunities) and confirms pagination/filtering behavior, but says nothing about result caps, default paging, or what the returned payload looks like.

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?

Three short sentences with the core purpose front-loaded and capability list following. No filler or redundancy.

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 read-only list tool with a fully documented six-parameter schema and readOnlyHint annotation, the description covers purpose and capabilities adequately. The lack of output schema means the response shape is undefined, but that is a minor gap for a list endpoint.

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 the schema already documents every parameter including filter syntax and comparator lists. The description merely names filter/order_by/depth/pagination generically, adding essentially nothing beyond the schema — the baseline 3 is warranted.

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?

"List/filter opportunities (deals)" gives a clear verb and resource, and the parenthetical disambiguates the domain term. It does not explicitly contrast itself with the get/create/update siblings, but the list verb is self-evidently distinct.

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 notes the supported capabilities (cursor pagination, raw filter/order_by, relation depth), which implies when the tool is useful. It never states when to prefer it over twenty_get_opportunity or twenty_list_metadata_objects, so usage is only implied.

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