moje_predmety

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

With no annotations provided, the description carries the full behavioral burden. It discloses the key behavior: what data is returned (code, name, faculty), how the period parameter works, and that an empty value means the current period. For a simple read-only list tool this is adequate, though it omits details like authentication or error behavior.

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 two short sentences, front-loads the core purpose and return fields, then explains the parameter. Every word earns its place and there is no redundant repetition of the tool name or schema.

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 a single optional parameter, an output schema, and no nested objects, this description is fully sufficient for an agent to call the tool correctly. It covers what is returned, the parameter format, and the default behavior.

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 description coverage is 0%, so the parameter meaning must come from the description. It does: 'obdobi' is explained with a concrete example ('podzim2026') and the empty-default semantic ('prázdné = aktuální'). This adds meaningful guidance beyond the bare 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 clearly states the tool lists enrolled subjects ('Zapsané předměty') for a given period and specifies the returned fields (code, name, faculty). It is specific enough to distinguish from siblings like moje_znamky or predmet_info, though it does not explicitly name an alternative tool.

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 context is implied: it is for retrieving a user's enrolled courses in a period, with an example period format ('podzim2026') and the default behavior when the parameter is empty. However, it gives no explicit guidance about when to use this tool instead of related siblings such as rozvrh or predmet_info.

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