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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'unwiderruflich' (irreversible) and 'samt aller Felder und Eintraege' (including all fields and entries), which are critical behavioral traits for a destructive operation. This provides meaningful context beyond the mere 'delete' verb.

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, concise sentence that front-loads the main verb and resource. Every word earns its place, with no redundancy or filler. The key behavioral caveat (unwiderruflich) is included without expanding length.

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 tool with one required parameter and no output schema, the description sufficiently covers the essential context: what is deleted, the irreversibility, and the cascade to related data. It lacks some depth (e.g., return format or auth requirements), but given the low complexity, it is reasonably complete.

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 describes a single required integer param `tracker_id`, and the description does not add any semantic detail about this parameter. With schema description coverage at 0%, the description fails to compensate by explaining the parameter's role or format. The parameter name is self-explanatory, but the description adds no value beyond the schema.

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 states 'Loescht einen Tracker unwiderruflich' – a specific verb ('loescht' – deletes) targeting the 'Tracker' resource. This clearly distinguishes it from sibling tools like delete_board, delete_card, etc. The addition 'samt aller Felder und Eintraege' clarifies the scope of deletion.

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 implies usage for deleting a tracker but provides no explicit guidance on when to use it versus alternatives or when not to use it. There is no mention of sibling tools or conditions that would make this tool inappropriate. Usage is inferred from the resource name rather than explicitly stated.

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