Longhand

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

No annotations are provided, so the description carries full burden. It discloses that it returns recent sessions with outcomes (shipped/fixed/stuck/exploratory), which adds behavioral context. However, it lacks details on permissions, rate limits, pagination, or error handling, which are critical for a read operation with multiple parameters.

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 two concise sentences with zero waste: the first defines the tool's purpose and output, and the second explains its use case. It is front-loaded and efficiently communicates essential information without redundancy.

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 no annotations, no output schema, and low schema description coverage, the description is moderately complete. It covers the tool's purpose and basic behavior but lacks details on return structure, error cases, and full parameter semantics. For a 4-parameter tool with complexity in filtering, this is adequate but has clear gaps.

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 low at 25%, with only 'limit' having a description. The description adds value by implying 'since' and 'until' filter recent sessions and 'project_id' specifies the project, but does not explain parameter formats (e.g., date formats for 'since'/'until') or constraints beyond the default limit. It partially compensates but leaves gaps.

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 'session-level timeline for a project' with 'recent sessions' and their outcomes, providing a specific verb (returns) and resource (timeline). It distinguishes from siblings like 'get_session_timeline' by focusing on project-level aggregation rather than individual sessions, though the differentiation could be more explicit.

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 implies usage for a 'bird's-eye view of what's been happening in a project lately,' suggesting it's for recent project overviews. However, it lacks explicit guidance on when to use this versus alternatives like 'get_latest_events' or 'list_sessions,' and does not mention prerequisites or exclusions, leaving some ambiguity.

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