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

Annotations already indicate this is not read-only, and the description confirms a create operation but adds no additional behavioral context such as required permissions, idempotency implications, or what happens on success/failure. With no output schema, the description does not disclose return behavior or side effects beyond creation.

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 description is a single focused sentence that includes the action, resource, endpoint, and parameter meaning. Every part earns its place and nothing is redundant.

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?

Given there is no output schema, no detailed parameter schema, and no guidance on entity structure, the description is too sparse for an agent to invoke the tool correctly without further research. It does not explain required fields, response format, or how to construct the data object beyond 'per official API'.

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?

The schema only defines 'data' as an object with additionalProperties, providing no property-level detail. The description adds that 'data' is the entity body per the official API, which is minimal but meaningful context; however, it does not compensate fully for the 0% schema coverage since it points to external documentation rather than explaining the structure.

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 clearly states the tool creates litigations/processes with a consolidated view, and it includes the explicit endpoint (OData POST /Litigations). It is specific enough about the resource, though it does not directly distinguish itself from the sibling legalone_create_lawsuits beyond the name.

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 guidance is provided about when to use this tool versus alternatives such as legalone_create_lawsuits or legalone_update_litigations. The description only states what it does, not when or why it should be chosen.

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