boond_opportunities_get

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

No annotations are provided and there is no output schema, so the description carries the full behavioral burden. It only says 'Get', without disclosing response shape, not-found/error behavior, authentication needs, or confirming the operation is read-only beyond the verb itself.

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 entire description is a single, front-loaded sentence with no filler. Every word carries meaning, and it is optimally concise for a simple get-by-ID operation.

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 the low complexity, the description plus the required 'id' parameter is enough to attempt a call. However, without an output schema or annotations, the absence of any comment on the return value or error behavior leaves a small but real gap for an agent trying to 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?

With one parameter and 0% schema description coverage, the description compensates by defining 'id' as the opportunity ID through the phrase 'by ID'. It does not specify the ID format or source, but for a single-parameter lookup that is a reasonable amount of added meaning.

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 states a specific verb, 'Get', and a specific resource, 'an opportunity', and the 'by ID' qualifier makes it clear this is the singular lookup variant. It does not, however, explicitly contrast with sibling tools such as boond_opportunities_search, so it stops short of a 5.

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?

'By ID' implies the caller must already have an opportunity ID, which is the primary usage signal. There is no explicit when-to-use guidance or comparison against boond_opportunities_search, leaving the choice of this tool versus the search variant implied rather than stated.

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