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

With no annotations provided, the description carries the full burden, and it delivers: it discloses that null rule fields are omitted and never match filters, that include=['offers'] returns a deduplicated top-level offers list with challenge-to-offer references, and that the result is a rules snapshot, not an outcome simulation. These are non-obvious behaviors an agent must know.

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 four sentences, front-loaded with the core purpose, and every sentence earns its place: scope, filter categories, id-based retrieval, offer inclusion, null-field behavior, and sibling-tool routing. There is no filler or repetition.

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 36-parameter tool with no annotations and no output schema, the description is remarkably complete: it explains purpose, scope, null handling, offer inclusion, and which sibling to use for outcomes. The only noticeable gap is the lack of any detail about the top-level response shape or pagination beyond what the schema already states, which is a minor omission given the schema's richness.

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 coverage is 100%, so the baseline is 3. The description adds genuine value by explaining how propfirmId and challengeId change the query scope, what include=['offers'] returns and how offerIds link to challenges, and that null rule fields cannot match filters. This exceeds a bare restatement of the schema.

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 opens with a specific verb and resource: 'Search funded-account challenges across all visible prop firms.' It also distinguishes itself from outcome-oriented siblings by stating 'This returns each challenge's listed rules and terms, not outcomes,' making its purpose unmistakable even without opening the schema.

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?

Usage guidance is explicit both within the tool ('Pass propfirmId to list one firm's challenges, or challengeId to fetch specific ones') and across alternatives ('to simulate... pass its ids to propfirms_simulate or propfirms_pass_rates, and to screen... use propfirms_validate_strategy'). It also clarifies what the tool does not do, which helps an agent choose correctly.

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