get_fee_status

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so "Read-only" mostly repeats structured data. The one genuine addition is the required "tuition fees right", which tells the agent an authorization prerequisite exists that the annotations do not express; no pagination, error, or rate-limit behavior is disclosed.

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?

Two short sentences, front-loaded with the resource and the returned fields, with the access requirement last. The internal endpoint name (wbservicesbasic.studienbeitragsstatus) is jargon an agent gains little from, but nothing is padded or 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?

With no parameters, no output schema, and rich annotations, the description supplies the remaining essentials: what data comes back and that a specific right is needed. It stops short of explaining failure modes when the right is missing, which keeps it from a 5.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The listed fields (semester, open amount, deadline) describe the result shape rather than inputs, which is a mild bonus rather than a parameter clarification.

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?

States a specific verb and resource ("Read wbservicesbasic.studienbeitragsstatus") and names the data returned: semester, open amount, and deadline. That makes the tool's purpose unmistakable, though it never contrasts itself with sibling tools such as get_grades or list_semesters.

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 a prerequisite ("Requires the tuition fees right"), which implicitly tells the agent this only applies to fee-related queries. It offers no explicit when-to-use framing or named alternatives, so the routing guidance is only implied.

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