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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds meaningful context beyond that: the data comes 'from their own pages' and prices are 'after any live code', disclosing sourcing and price-computation semantics. No rate limits or pagination are mentioned, but the bar is lower with full annotation coverage.

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?

Front-loads the resource and content before the usage triggers, and the whole thing is compact. The trailing 'Args:' enumeration is largely redundant against a 100%-documented schema, a minor waste, but overall the structure is tight.

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 read-only, all-optional filter tool with no output schema, the description usefully enumerates the returned fields (rules, discount codes, prices, platforms), which compensates for the missing output schema. Enough to call correctly, though it could clarify result shape per cold vs. filtered queries.

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% and the schema descriptions are richer than the tool description itself (e.g. account_usd, country, rule all have detailed semantics). The description merely re-lists the argument names ('firm; rule; account_usd; country; asset; on_chain; max_price_usd') without adding meaning. Baseline 3 is correct.

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 (perps prop firms) and enumerates the data returned: rules, challenge prices after live codes, discount codes, country, platforms, assets, max allocation. The title reinforces the domain (perpetual futures prop firms), clearly distinct from the perps market/history siblings. It does not explicitly name a sibling to differentiate against, keeping it at 4.

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?

Provides concrete trigger queries ('crypto prop firm rules', 'X discount code', 'cheapest $50K challenge', 'prop firms in the UAE') that map well onto the filters. This is strong when-to-use guidance, though it names no excluded cases or alternative tools.

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