gryps_get_market

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

No annotations provided. Description lists return fields but does not explicitly state read-only nature, permissions, or side effects. For a 'get' operation, it's adequate but not fully transparent.

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?

Single sentence that efficiently conveys purpose and key return fields. No wasted words, front-loaded with value.

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?

No output schema, but description lists return fields explicitly. Covers main aspects of a single-market detail tool. Could include more on response format or size, but sufficient for the agent to understand what to expect.

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?

100% schema coverage. Description provides examples for symbol parameter (BTC, XAU, SEIUSDT), same as schema description. Adds no new meaning beyond schema, baseline 3.

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?

Clear verb and resource: get full detail for one Gryps market. Lists specific fields (leverage, notional bounds, fee schedule, funding epoch, categories), distinguishing it from siblings like gryps_list_markets (list all) and gryps_get_funding (funding specific).

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?

Implies use when needing full market details, but no explicit when-to-use or when-not. No mention of alternatives like gryps_list_markets for overview or gryps_open_interest for interest data.

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