SENTn Opportunity Intelligence

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does add useful context by saying the tool returns a 'public snapshot' and a 'canonical SENTn URL,' implying a read-only public-info retrieval. However, it never explicitly states that the operation has no side effects, and it does not mention what happens if the ID does not exist or is invalid.

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 a single, front-loaded sentence. Every clause adds essential information: the precondition, the resource, and the return value. There is no filler or redundancy.

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 simple one-parameter retrieval tool with no output schema, the description covers the main needs: when to use it, what the parameter is, and what the tool returns. It lacks explicit error handling or read-only guarantees, but these are less critical for such a small, focused tool.

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 0%, so the description must compensate. It does add meaning by identifying the parameter as a 'SENTn opportunity ID,' which is crucial for correct invocation. But it does not elaborate on where to find this ID or how it relates to the schema's pattern constraints, leaving some room for misinterpretation.

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 tells an agent exactly what the tool does: given a known SENTn opportunity ID, it returns the public snapshot details and canonical SENTn URL. It uses a clear conditional ('when an agent already knows a SENTn opportunity ID') and names the specific resource (opportunity) and expected outputs, making it easily distinguishable from search_opportunities.

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 explicitly states when to use the tool: when the agent already has the opportunity ID. This implies that search_opportunities should be used when the ID is not known, but it does not name the sibling or explicitly state the exclusion. The condition is clear enough for an agent to select this tool correctly.

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

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

With no annotations, the description carries the behavioral disclosure burden. It communicates that results are ranked, that filtering is optional, and that pagination is supported, all of which are useful. It does not mention response format, default behavior, or whether results are read-only, though 'retrieve' and 'browse' strongly imply a read operation.

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?

One concise sentence front-loads the primary use case and packs in the ranked-page, category filtering, and pagination behaviors. It is slightly dense but contains 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?

Given no annotations, no output schema, and no parameter descriptions, the description is too thin to fully guide a correct call. It explains the main scenario but leaves important details unspecified: what the response looks like, whether limit has a default, how cursor is obtained, and how category values are formatted. A few clarifying clauses would substantially improve completeness.

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 0%, so the description must compensate by explaining the parameters. It only alludes to category and pagination in prose, but does not clarify the meaning of limit, cursor, or their interaction. An agent cannot confidently know what values to supply for these three undocumented parameters.

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 names a specific verb and resource: 'browse SENTn's opportunity intelligence library' and 'retrieve a ranked page of opportunities.' It also captures the distinct capabilities of filtering by category and paginating, making it reasonably distinguishable from the sibling get_opportunity even without an explicit comparison.

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?

It opens with 'Use when an agent needs to browse,' which gives clear context for when the tool is appropriate. However, it never says when not to use it or how it relates to the sibling get_opportunity, so the agent is left to infer the boundary between searching/browsing and fetching a single opportunity.

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