get_stadtratsbeschluss_detail

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

Annotations already indicate readOnly, idempotent, non-destructive. The description adds that the tool returns Markdown, and errors for missing or out-of-range (pre-Feb 2025) resolutions, providing extra behavioral context beyond annotations.

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 concise, structured with Args and Returns sections, and every sentence adds value without redundancy.

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 the simple one-parameter tool, with thorough description of return format and error conditions, and with annotations covering safety, the description is complete and provides all necessary information for an agent to use the tool correctly.

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 parameter 'beschlussnummer' is well-defined in both the schema (pattern, format, example) and the description (explains where to find the number). Despite 0% schema description coverage from context, the description fully explains the parameter meaning and format.

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 retrieves metadata of a single Stadtratsbeschluss by its number, listing the returned fields. It distinguishes from siblings like search_stadtratsbeschluesse and get_beschluesse_by_departement which serve different purposes.

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 specifies the required parameter format and provides example inputs. It implies usage via the single parameter but does not explicitly state when not to use or compare to alternatives, though siblings make the differentiation clear.

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