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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds genuinely new behavioral context: the fixed 25-per-page paging behavior, the subset of deal fields returned, and the underlying endpoint. It doesn't discuss rate limits or ordering defaults beyond what the schema already states.

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 dense sentence with the key scoping and paging facts front-loaded, followed by the endpoint. Efficient, though slightly crammed with parenthetical asides.

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 4-param schema and no output schema, the description covers scope, paging and returned fields. Only ambiguity about the response envelope or total counts remains, which is minor.

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 page, sort, sort_type and view_id. The description adds minor value by restating the page size and the origin of view_id, but nothing beyond the schema baseline.

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 ('List the deals in a view') plus the scope constraint (driven by view_id) and the returned fields, which cleanly separates it from get_deal and from view-listing siblings. An agent can pick it without opening the schema.

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 parenthetical '(view_id from freshsales_list_deal_views)' gives the prerequisite and points to the sibling that produces the required id. It does not say when to prefer this over e.g. freshsales_search or freshsales_list_sales_activities, so it stops short of full routing guidance.

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