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

With no annotations, the description carries the transparency burden. It discloses that the response includes financial details and offering terms, but it does not mention that this is a read-only operation, pagination behavior, rate limits, or the exact response structure. The description is not misleading but is incomplete.

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 description is two sentences and reasonably sized. The first sentence repeats the tool's name ('FMP Latest Crowdfunding Campaigns API') which is slightly redundant, but the second sentence adds valuable context. Overall, it is efficient with minimal waste.

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?

This is a simple paginated list tool with no output schema, so the description should clarify what data is returned and pagination behavior. It mentions financial details and offering terms, but lacks specifics on response fields or how page/limit affect the output. It is adequate but not fully complete.

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?

The input schema already provides full descriptions for both parameters (page and limit) with 100% coverage, so the tool description adds no additional semantic value. Baseline score of 3 applies because the schema handles parameter documentation.

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 clearly identifies the tool as retrieving the most recent crowdfunding campaigns, using 'Discover' as the verb and specifying the scope ('most recent'). It effectively distinguishes from sibling tools like getCrowdfundingCampaignsByCIK and searchCrowdfundingCampaigns by highlighting its list-latest nature.

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 provides context by stating it helps users stay informed on actively raising funds, which implies use for a broad, recent campaign list. However, it does not explicitly mention alternatives or conditions when this tool should be avoided in favor of search or by-CIK variants.

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