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 mentions the record is 'rich source-backed' with 'confirmed AWS/MCP presence', but does not disclose read-only behavior, potential errors, authentication needs, or response structure. Lacks sufficient transparency for a tool with zero annotation context.

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 sentence that efficiently delivers the core purpose and key distinguishing features. No wasted words, and the most important information is front-loaded.

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 is simple with one parameter and no output schema. The description gives enough to understand basic usage, but lacks details on return format, edge cases, or how it relates to siblings. Adequate for a simple get-by-id tool, but could include more behavioral context.

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?

The schema has a single 'id' parameter with no description (0% coverage). The description compensates by clarifying that the id is a 'market entity id', giving it semantic meaning beyond the bare schema definition. That is meaningful addition.

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 ('Return') and resource ('xOmniMarket record for one market entity id'), and adds distinguishing details ('rich source-backed', 'confirmed AWS/MCP presence'). It clearly differentiates from siblings like search_market, which implies querying, by focusing on retrieving a single record by ID.

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 implies the tool is for fetching a specific record when an entity ID is known, but it does not explicitly state when to prefer it over alternatives such as search_market or compare_market_items. The usage context is implied rather than explicit.

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