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

No annotations are provided, so the description carries the full behavioral burden. It does disclose real behavioral traits beyond the schema: which sub-collections are returned and that speech text requires a separate get_document call. It omits any statement about read-only nature, error behavior, permissions, or pagination, which for a zero-annotation tool leaves meaningful gaps.

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?

One dense, run-on sentence with a heavily nested content list. It is front-loaded with the resource, which helps, but much of the enumeration duplicates what a return value/output schema would convey and crowds out actionable guidance such as parameter format.

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?

An output schema exists, so the description need not explain return values, yet it spends nearly all its length doing exactly that. Given the tool's complexity, the definition is workable but thin on the two things the schema cannot supply: how to form the ID and when this tool beats its siblings.

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 coverage is 0% for the single parameter, so the description must compensate. It partially does by saying the input is the 'doc_id eines Dokuments vom Typ vorgang', but this wording conflicts with the declared parameter name and type (vorgang_id: integer), creating ambiguity about whether a numeric Vorgang ID or a document ID is expected.

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 names a specific resource (a DIP Vorgang / legislative procedure) and enumerates the concrete sub-entities it exposes, so an agent knows it is a rich detail-retrieval tool rather than a search. It also names a sibling (get_document) for speech text, giving partial differentiation. However, the purpose is buried under a long content inventory rather than stated as a crisp verb+resource.

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?

Usage is only implied: the agent learns it must call get_document to obtain the reden text, which is a genuine routing hint. There is no explicit when-to-use vs search/find_actor/get_relations, no statement of prerequisites for the ID, and no when-not-to-use guidance.

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