Get a prop firm

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that uncaptured null fields are omitted and that challenges reference offers through offerIds, which are meaningful behavioral details beyond the name. It could mention read-only behavior more explicitly, but 'get' plus the dossier framing strongly implies a safe retrieval.

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 dense but every sentence contributes: what the tool returns, how to find the slug, how nulls and offer references behave, and when to use a sibling tool. It is front-loaded with the core purpose and keeps auxiliary guidance compact.

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?

Given there is no output schema and no annotations, the description does a strong job of setting expectations for a complex dossier response: it enumerates the major sections, explains omission behavior, clarifies cross-references between challenges and offers, and points to search and pass-rate tools. An agent has enough context to invoke the tool correctly and interpret the result.

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 coverage is 100% and the single parameter is already described as a public firm slug. The description adds value by stating that the parameter is used by slug and pointing to propfirms_search for discovering valid slugs, which helps the agent supply a correct value.

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 one prop firm's full dossier by slug, with an explicit enumeration of the contents (profile, challenges, offers, overview). It distinguishes itself from sibling tools such as propfirms_search, propfirms_challenge_rules, and propfirms_pass_rates by focusing on the complete consolidated record.

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 direct usage guidance: use this to get a full dossier by slug, find slugs via propfirms_search, and use propfirms_pass_rates for simulated pass odds. This explicitly routes to alternative sibling tools, making the selection criteria clear.

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