get_assumption

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

Describes return value details (typed fields, exclusion, override layer, soft-deleted flag) but does not explicitly state that the operation is read-only or disclose any side effects, permissions, or error conditions. No annotations provided, so description carries the burden but falls short of full 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?

Two sentences, no redundancy, uses backticks for clarity, front-loaded purpose.

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?

Covers return values well and explains merge logic, but omits explanation for server_version parameter and does not mention potential error scenarios. Output schema exists, mitigating some gaps.

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 descriptions exist for model_id and assumption_id but not for server_version (67% coverage). Description adds no additional meaning beyond what the schema provides for these 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?

Clearly states the tool gets a single assumption with override applied, lists return fields, and distinguishes from list_assumptions by noting it mirrors merge logic for one entity.

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 referencing list_assumptions' merge logic, but does not provide explicit when-to-use or when-not-to-use guidance compared to other assumption-related sibling tools like add_assumption, edit_assumption, etc.

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