get-person-logged-time-summary

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

No annotations are provided, so the description must disclose behavioral traits. It only states it 'gets a summary' and mentions billable/non-billable hours, but does not detail the aggregation, return format, any limitations, authentication needs, or whether it is read-only. The read-only nature is implied but not explicitly stated.

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 sentence that succinctly conveys the tool's purpose. It is front-loaded, contains no redundancies, and every word provides value.

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 5 parameters, no output schema, and no annotations, the description is minimally adequate. It explains the tool's core function but omits details about what the summary contains (e.g., total hours, daily breakdown) and how results are structured. The agent has to infer behavior from the tool name and parameters.

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?

All 5 parameters have descriptions in the input schema, achieving 100% coverage. The description adds the context that the summary includes billable/non-billable hours, aligning with the 'billable' parameter. However, it does not clarify parameter value formats or relationships beyond 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?

The description clearly states the tool retrieves a logged time summary for a specific person, including billable/non-billable hours. It differentiates from sibling tools like get-project-logged-time-summary by specifying the scope 'for a specific person', though it could explicitly contrast with similar report tools.

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 such as get-project-logged-time-summary or get-time-report. There are no conditions, prerequisites, or when-not-to-use hints.

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