get_my_attendance

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

No annotations are provided, so the description carries full burden. It states this is a read operation ('Get'), but doesn't disclose behavioral traits like authentication requirements, rate limits, pagination behavior, error conditions, or what happens if no records match. The description is minimal and lacks critical operational context.

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 appropriately concise with two sentences: a clear purpose statement followed by parameter documentation. The parameter explanations are brief but informative. No unnecessary verbiage, though the formatting with indentation could be cleaner.

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 the tool has an output schema (which handles return values), the description's main gaps are in behavioral transparency and usage guidelines. For a simple read tool with two parameters, the description is minimally adequate but lacks context about authentication, error handling, and sibling differentiation. It meets basic needs but leaves important questions unanswered.

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 schema provides no parameter descriptions. The description adds basic semantics for both parameters: 'limit' as 'Max records to return (default 10)' and 'month' as 'Filter by month (YYYY-MM format, optional)'. This covers purpose and format but lacks deeper context (e.g., what happens if month is invalid, if limit applies before/after filtering).

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's purpose: 'Get attendance records for the current user.' It specifies the verb ('Get') and resource ('attendance records') with scope ('for the current user'). However, it doesn't explicitly differentiate from sibling tools like 'get_my_leaves' or 'get_my_tasks' which also retrieve user-specific data.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the user must be logged in), nor does it contrast with other attendance-related tools (none are listed among siblings). The only implied usage is for retrieving personal attendance data.

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