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

With no annotations, the description carries the full burden. It mentions 'current verified' and a 'reusable 24-hour AgentWork pass', but does not clarify what verification means, how the pass works, or what happens if the pass is invalid or the opportunity is not found. The behavior is only minimally disclosed and the pass reference is vague.

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 short sentence, front-loaded with the core action. It is concise, but the phrase 'using the same reusable 24-hour AgentWork pass' is somewhat unclear and could be considered extraneous. Overall, it is efficient but not perfectly structured.

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?

The tool has no annotations and no output schema, so the description must cover return values and error behavior. It does not mention what the response object looks like, any potential errors, or prerequisites beyond the vague pass reference. The description is too sparse for a tool that must fully inform the agent on its own.

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. However, it does not explain what the 'id' parameter represents or how to obtain it. The description only says 'Get one... opportunity', implying the id is an opportunity identifier, but it never explicitly says 'by ID' or provides any context for the parameter. This is insufficient given the lack of schema descriptions.

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 states the tool's function: to retrieve a single, current, verified opportunity. The verb 'Get' plus the resource 'opportunity' is specific, and the 'one' distinguishes it from list/search tools. It doesn't explicitly contrast with sibling tools, but the purpose is clear enough.

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?

No guidance is provided about when to use this tool versus alternatives like search_work or search_services. There is no mention of having an opportunity ID, when to prefer this over a search, or any exclusions. The description lacks any usage context.

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