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

Beyond the readOnlyHint annotation, the description discloses the default behavior when no search term is provided (most recently modified) and confirms the output is the IDs needed by session_lesen. This adds meaningful behavioral context.

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 three compact, purposeful sentences: what the tool does, when to use it, and its default behavior. No wasted words and the key guidance is front-loaded.

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?

For a low-complexity, read-only search tool with zero required parameters, the description covers the trigger conditions, scoping, default behavior, and output purpose. The absence of a return-format description is minor because the tool is clearly a lightweight ID lookup feeding session_lesen.

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 100%, so the schema already documents both parameters. The description adds only the empty-search default behavior but does not add meaning for 'anzahl' beyond the schema; the baseline score of 3 is appropriate.

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 verb 'Findet' and the resource: the user's workshops and seminars in Sessionario. It also differentiates the tool from the sibling session_lesen by explaining that it supplies the IDs that session_lesen needs.

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?

The description gives explicit trigger phrases ('meiner Session', 'dem Workshop bei X', 'Termin') and instructs the agent to use this tool first. It names session_lesen as the dependent follow-up but does not explicitly exclude other sibling tools.

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