List Productivity Logs

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by explaining the default date behavior (current date if no date parameters) and pagination details (page, per_page, pagination metadata), which are not covered by annotations.

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 reasonably concise and well-structured: purpose first, then date parameter explanation, usage, response format, pagination, required param, and API info. It front-loads the core purpose. The inclusion of a documentation link is helpful but slightly extends length.

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 8 parameters and no output schema, the description covers key aspects: default date behavior, filtering options, pagination, required project_id, and a link to further documentation. It is complete enough for a list tool without explaining every return field.

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 coverage is 100%, so baseline is 3. The description adds context beyond schema by explaining the default date behavior when no date parameters are provided and by explicitly stating that page and per_page control pagination with metadata in the response.

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 that the tool returns all Productivity Logs for the current date, with a specific verb ('Returns') and resource ('Productivity Logs'). It differentiates from sibling list tools by specifying the exact resource type and default date behavior.

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 gives usage context ('Use this to enumerate Daily Log records when you need a paginated overview, to find IDs, or to filter by query parameters') but does not explicitly state when NOT to use it or mention alternative tools among siblings.

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