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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely useful behavior beyond that — ordering ('newest first'), optional date-bracketing, and an explicit auth requirement ('Needs the user's Cotlet API key with access to this app'). It stops short of disclosing result limits or pagination for a list endpoint.

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?

Front-loaded and reasonably tight, but the first sentence ('date, people on site, weather, materials and notes') and the third sentence ('notes, the people on site, deliveries and the weather') redundantly enumerate the same log contents, which costs a little space.

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 read-only list tool with no output schema, the description usefully sketches what each returned log contains and the ordering, and annotations cover the safety profile. The remaining gap is pagination/result-limit behavior, which matters for a list endpoint.

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 100% (project_id, from, to are each documented), so the schema carries the parameter burden and 3 is the baseline. The description confirms the date pair behaves as an optional range but adds no format or boundary semantics 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?

States the verb ('Returns the daily logs'), the resource ('Daily logs on a project') and the scope ('of one project'), plus the fields a log carries. It is clearly a read/list operation distinguishable from the sibling contractor-foreman_create_daily_log, though no sibling is named 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?

Usage is only implied: the agent can infer it retrieves logs for one project optionally narrowed by date. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for related data.

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