Get Hostel Summary

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

With no annotations, the description must carry the behavioral burden; the 'get_' name and 'snapshot' framing imply a read-only composite read, which is reasonable. It usefully discloses that attendance is returned as yes/no per date, but says nothing about permissions, rate limits, or paging, so it stops short of full disclosure.

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?

A single dense sentence that front-loads the 'Hostel snapshot' identity and then lists the three payload parts in order of importance. No filler, though the parenthetical detail makes it slightly heavy.

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?

An output schema exists, so return details need not be explained, and the description still usefully previews the three returned sections. For a single-optional-param read tool this is largely sufficient, with only usage routing left unaddressed.

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% for the single `days` parameter, so the description must compensate, and it does: 'the last `days` days (yes/no per date)' explains both the meaning and the return granularity. It does not restate the schema default of 14, but that is already in 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?

States a concrete verb+resource ('Hostel snapshot') and enumerates the three payloads it returns: allotment with hostel/room/status/dates, a per-date attendance roll, and profile hostel data. This lets an agent distinguish it from get_attendance_summary and get_profile, though it never explicitly names those siblings.

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?

No guidance on when to choose this over get_attendance_summary (general attendance) or get_profile (general profile data), even though the description's scope overlaps both. No prerequisites, exclusions, or call conditions are stated.

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