boond_absences_get

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

With no annotations, the description carries the full burden. 'Get' clearly implies a read-only operation, which is accurate, but it does not disclose what happens if the ID is not found, whether there are rate limits, or what the response format is. For a simple getter, this is adequate but not rich.

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, tight sentence with no filler. It front-loads the action and scope efficiently.

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 simple get-by-ID tool, the description fails to mention what is returned (e.g., the absence object) and does not address error cases. With no output schema and no annotations, the agent is left without essential details about the expected response, making the description incomplete for a tool this simple.

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 has one parameter 'id' with zero description coverage. The tool description adds only 'by ID', which does not elaborate on the ID's format, source, or any constraints beyond the schema's minLength. Since schema coverage is 0%, the description should compensate but does not provide meaningful added information.

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 'Get an absence by ID' clearly states a specific verb and resource, and the ID parameter anchors it as a single-record retrieval. It is distinguishable from its search sibling by the explicit 'by ID' scope, though it does not name the sibling explicitly.

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 is provided on when to use this tool versus the search alternative (boond_absences_search). The description does not mention that one would typically search first to obtain the ID, nor does it state any exclusions or prerequisites. This leaves the agent to infer usage context.

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