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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly spends its words on semantics instead: a 30-day window for open issues, the rule that archived/completed/demo projects count nothing unless demo=true, and the cap of 20 activity items. That is genuinely additive context not derivable from the 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?

Front-loaded with purpose and endpoint, then the three returned sections in order; information-dense rather than padded. The single long sentence with stacked parentheticals is slightly hard to parse but every clause carries content.

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?

With no output schema, the description does the work of describing the return payload (per-list done of total, open issues bucketed open/acknowledged/in progress, newest 20 activity items with who and when). For a two-parameter read tool this is close to sufficient; only the project_id format and the response envelope remain unstated.

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 50%: the demo parameter is already documented in the schema, and the description mostly restates its effect (with the useful addition that archived/completed projects also count zero). project_id has no schema description at all, though the ':id' in the endpoint hints at its role. Adequate but not compensating for the gap.

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 a specific verb+resource ('A project's progress and insights') and even cites the backing endpoint GET /projects/:id/insights, then enumerates the three sections returned. It never names a sibling (e.g. tascan_project_digest or tascan_get_project) as an alternative, so differentiation from adjacent read tools is left implicit.

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 trailing 'Read tier.' signals it is a non-mutating read and the demo flag rule gives a conditional usage hint, but there is no explicit when-to-use or when-not-to-use guidance versus siblings like project_digest, get_project, or org_analytics.

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