attendance_passage_by_id

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

With no annotations, the description carries the burden of disclosing side effects; the verb 'Get' makes clear this is a read-only lookup. However, it does not describe not-found behavior, response shape, or any access requirements, so transparency is only minimal.

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?

One short sentence with no filler; every word carries meaning and the verb is front-loaded. It is a model of concise tool documentation.

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 one-parameter, no-nested-object read tool, the description covers the core operation and return cardinality. It still relies on sibling names for routing and provides no output or error details, but the task is simple enough that this is near-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 input schema already documents pk as 'Passage ID' with 100% coverage. The description's 'by its ID' simply restates that semantic, adding no new format, constraints, or edge-case guidance; baseline 3 applies.

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 action ('Get'), a precise object ('single passage record'), and a lookup criterion ('by its ID'). The singular scope and ID-based lookup differentiate it from siblings like attendance_passages_by_date and attendance_insert_passage.

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 the tool is for retrieving one specific passage when its ID is known, but it does not explicitly state when to use it instead of date-based or other passage tools. No alternatives or exclusions are named, leaving routing inference to sibling names.

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