Get B2match opportunity

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

Annotations already cover read-only, idempotent, non-destructive behaviour, yet the description adds a non-obvious runtime trait: the marketplace menu path is resolved automatically, with path as an escape hatch. It does not disclose failure modes (e.g. what happens if the id is from the wrong id space) or pagination/return shape, so it stops short of a 5.

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 short sentences, all front-loaded with the action first, then the id-sourcing rule, then the override. Every clause carries operational information; nothing is boilerplate.

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 no output schema the description could say more about what a fetched opportunity contains, but for a simple single-object read with fully documented parameters and a clear id contract, an agent has enough to call it 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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning the schema cannot: the opportunity_id must be a published marketplace id rather than a participation id. The path parameter's auto-resolution behaviour is restated rather than extended, keeping it below 5.

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 verb and resource ("Fetch a marketplace opportunity") and immediately distinguishes itself from the sibling list_opportunities, which supplies the id. An agent can tell this is the single-object lookup that follows the listing call.

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 names the prerequisite tool ("Use the id or url from list_opportunities"), warns that ids from my_participation are a different id space and will not work, and states the path override condition. That is a real when/when-not plus an alternative source, not just implied usage.

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