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

Annotations only declare the safety profile (non-read-only, non-idempotent, closed-world, non-destructive); the description adds substantial behavioral detail beyond that: per-product pricing, automatic acceptance/decline, fixed-price quote on acceptance, delivery windows of 7/14 days, 'Nothing is owed until payment,' and the receipt/status flow. It never warns that repeat submissions are not idempotent and may create duplicates, which is the notable gap.

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?

The core action is front-loaded and almost every clause carries weight (pricing, SLA, payment terms, receipt, privacy notice). The pricing parentheticals ('€5 to 31 December 2026, then €10') make the middle dense and slightly hard to parse, but there is little outright filler.

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 10-parameter, nested-input submission tool with no output schema, the description covers the business workflow well but leaves the input side largely undocumented and does not describe what the immediate response contains beyond 'accepted or declined.' An agent can call it, but cannot confidently fill most fields from the description.

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 only 20% across 10 parameters, so the description must compensate, yet it only elaborates on the product enum (answer/brief/map) with prices and page counts. It says nothing about subjectType, companyName, budget, topics, outputFormat distinctions, maximumAgeDays, or consentToStore, leaving most of the input surface unexplained.

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 opening states a specific verb and resource: 'Ask SNTL one research question about a space company or market, and choose the product.' It also positions the tool in a workflow by naming check_research_status as the follow-up. It does not distinguish itself from the other sibling, respond_to_research_offer, so it falls short of a clean 5.

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 description gives clear usage context: one question, choose a product, accepted or declined automatically, and explicitly says to 'Keep the receipt and return with check_research_status.' It also imposes a content restriction ('Do not include contact details or personal information'). It stops short of stating when not to use it or how it relates to respond_to_research_offer.

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