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

Annotations already carry readOnly/idempotent/destructive safety, so the bar is lower; the description adds the news-feed semantics and the citation nuance that a syndicated item's URL points to the original publisher, not CrowdSpace. This is useful behavioral context beyond the structured fields, though it does not discuss pagination or freshness windows.

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 sentences, no filler: content, filters, then usage guidance and the caveat. Information is front-loaded and each sentence earns its place.

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 a comprehensive schema and an output schema present, the description supplies the missing semantic context: when to use, when not, citation behavior, and distinction from the catalogue. An agent has everything needed to select and invoke the tool correctly.

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?

Input schema covers 100% of parameters with descriptions, so the baseline is 3. The description reinforces the filter dimensions (category, kind, date range) but adds little beyond schema text; 'editorial' and 'syndicated' are already defined in the kind parameter's description.

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 resource: 'Recent crowdfunding and P2P lending news' and enumerates the returned fields. It also differentiates itself from the sibling search_platforms ('news feed, not the catalogue'), so an agent can tell it apart from the most similar alternative.

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?

Explicitly gives the trigger ('what happened recently / any news about X') and explicitly excludes the alternate use ('Do NOT use it to establish facts about a platform'), naming search_platforms as the correct tool. This is textbook when/when-not routing.

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