get_deal

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

No annotations provided, so description must carry burden. It discloses endpoint (GET), read-only nature (tier: readonly-owner), and that it retrieves by ID. However, includes irrelevant create requirements which detract from transparency.

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?

Description is somewhat cluttered: first sentence is clear, but then includes irrelevant create info, a fragment 'by ID', endpoint mapping, and tier. Could be more concise and 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?

Adequate for a simple read tool with 2 parameters. Mentions endpoint and auth tier, but lacks description of return value structure (no output schema). The irrelevant create info reduces 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 documentation coverage is 50% (only 'properties' has description). Description adds little beyond 'by ID' and create constraints that are not relevant to this GET operation. Does not elaborate on the 'id' parameter or the default for 'properties'.

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?

Clearly states 'Get a single deal (sales opportunity) record', which specifies the verb and resource. Distinguishes from sibling 'list_deals' by indicating single record retrieval.

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 usage by ID, but no explicit guidance on when to use this tool vs alternatives. Includes irrelevant create constraints that could confuse. No exclusions or alternative tool names mentioned.

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