get-logged-time-timesheet

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

No annotations provided; description carries the full burden. It mentions organization by person and date but does not disclose other behavioral traits such as whether it aggregates time, what happens with missing data, or required permissions for reading this data.

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?

Single sentence that front-loads the core purpose and formatting info. No redundant words; each part adds 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?

No output schema exists, so description should explain return format or structure. It only says 'organized by person and date' but lacks specifics about grouping, totals, or pagination. For a tool with 5 parameters and no output schema, the description is insufficiently 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?

Input schema has 100% description coverage for all 5 parameters. Description adds no extra parameter-specific meaning beyond the schema. Baseline score of 3 is appropriate.

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?

Description clearly states verb 'Get', resource 'logged time in timesheet format', and specifies organization by person and date. Differentiates from siblings like get-logged-time or list-logged-time which likely return raw 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?

No explicit guidance on when to use this tool versus alternatives like get-logged-time, list-logged-time, or get-project-logged-time-summary. The description implies a timesheet view but doesn't state when it's appropriate.

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