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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'Read only: nothing in Profolio changes' is largely redundant. It does add genuine value by disclosing the required Cotlet API-key scope and by stating the return is a download link, but it omits pagination, file-expiry, or scope details for a link-returning export.

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?

Five sentences with repetition ('as a download link' stated twice) and a weak opening fragment that restates the title. The core fact — a channel-filtered lead export — is not front-loaded, and the UI-path details ('top right of Reports, Leads') add noise rather than signal.

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 one-parameter, no-required-input tool with annotations covering safety and no output schema, the description supplies the essentials: what it exports, the channel filter, read-only nature, auth requirement, and the download-link return. It stops short of explaining the link's lifetime or any rate limits, but nothing critical to correct invocation is missing.

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 100% and the single channel parameter is fully documented with enum values and a 'Default: all' note. The description only echoes this ('Pass a channel to export one channel only'), adding a marginal clarification that the filter is exclusive, so the baseline 3 is appropriate.

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 does convey that this exports leads to an Excel file, but the phrasing is tangled and UI-centric ('The Excel file Profolio exports from Reports, Leads', 'Runs the export option at the top right'). An agent can infer a read-only export of leads, but the verb+resource are buried in product-navigation jargon and no sibling (e.g. bayut_list_leads, bayut_get_lead) is distinguished.

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 only guidance is 'Pass a channel to export one channel only,' which is a parameter hint rather than a when-to-use rule. There is no statement of when to prefer this over bayut_list_leads or other lead tools, and no prerequisites beyond the API-key note.

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