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

No annotations are supplied, so the description carries the full load; it does disclose the shape of the response (request handling, returned data, scope/limits, fields, operations), which is valuable and implies a read-only lookup. It says nothing about failure behavior for unknown slugs, authentication, or whether the 'operations' list implies anything actionable.

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?

A single compact sentence with no filler, though it is a comma-separated inventory rather than being front-loaded with a clear statement of what the tool does.

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?

With no output schema and no annotations, the description does a reasonable job of previewing return contents, but it leaves the sole input undocumented and the proposition-versus-service terminology unresolved, which is a real gap for a one-parameter lookup tool.

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?

There is one parameter, slug, with 0% schema description coverage, and the description never explains what a slug is, where to obtain one, or its format/limits (maxLength 80 goes unmentioned). The reference to 'request fields' concerns the described service, not the input parameter, so it does not compensate.

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 enumerates what the tool returns (request behavior, outputs, scope and limits, fields, operations) which implies a detail-lookup for a single item, but it never states a verb or resource explicitly and shifts vocabulary from 'proposition' in the name to 'service' in the text. An agent can infer it is the detail counterpart to list_propositions, but only by guessing.

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 when-to-use guidance, no prerequisites, and no named alternative such as list_propositions for enumeration versus this tool for drill-down. The agent must infer the selection rule from the tool name alone.

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