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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the transport detail (POST /SalesQuote/SalesQuoteGet), which is mildly useful for a read performed via POST, but says nothing beyond annotations about result volume or ordering behavior.

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, front-loaded with purpose and return contents before filtering and endpoint. Nothing is padded, though the raw endpoint path adds little value for an agent choosing a tool.

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 no output schema, the description helpfully names the main returned fields, and read-only annotations cover safety while the schema fully covers parameters. Only ordering/pagination behavior is left to the schema, which is acceptable since the schema does state it.

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 all four parameters (limit, status, filters, quote_no) are already documented in the schema, including the no-page-offset behavior. The description's mention of filtering by quote number or status only restates what the schema provides, so the baseline of 3 applies.

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 sales quotes') and enumerates the salient returned fields (client, totals, status, rows), so the agent knows what it gets back. It does not distinguish itself from siblings like megaventory_list_sales_orders or megaventory_list_documents, leaving that inference to the name.

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?

'Filter by quote number or status' implies when the tool is useful, but there is no explicit when-to-use framing, no prerequisite (e.g. needing a quote number), and no pointer to an alternative listing tool when quotes are not the target.

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