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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing beyond a duplicated route string — no mention of what 'current' resolves to, whether it 404s when no current version exists, or what the payload looks like.

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 single substantive sentence is duplicated verbatim, which is pure waste, and the front-loaded content is a raw URL rather than a human-readable statement of effect. It is short, but the brevity comes from under-specification rather than efficiency.

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?

There is no output schema and 0% parameter coverage, so the description must carry the burden of explaining the returned 'current' negotiation object and its path parameters — it does neither. For a tool in a dense family of near-identical negotiation getters, this leaves the agent unable to distinguish or correctly call it.

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 description coverage is 0% and the two nested params (entity, id) have no documented meaning in the schema. The description's ':entity/:id' placeholders at least imply both are path parameters, but it never says what 'entity' denotes (entity type? contract/lease?) or the expected id format, so it does not compensate for the coverage gap.

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 only restates the raw route 'GET /api/negotiation/:entity/:id/current' plus an operation ID, which is essentially a restatement of the title/name. It never explains what the 'current' negotiation resource is (current version? current state of the negotiation?) or how it differs from sibling endpoints like get_negotiation_by_entity_by_id_draft, _redline, and _version.

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?

There is no statement of when to use this tool versus the many sibling negotiation endpoints (draft, redline, version, versions history). The only actionable guidance is the pointer that 'describe_operation provides native request schemas', which is a schema-lookup hint rather than usage guidance.

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