Get Context Snapshot

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the read-only safety profile. The description adds that the snapshot combines summary, blockers, and pending tasks, which is useful but does not disclose additional behavioral traits such as output format, behavior when the optional project is omitted, or performance characteristics. This is adequate but not comprehensive.

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 a single, direct sentence that immediately states the action and resource, then efficiently lists the three composed components. No redundant or filler words are present.

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 simple read-only tool with one optional parameter and no output schema, the description sufficiently conveys the content of the snapshot (summary, blockers, pending tasks). It could arguably mention the output structure or the role of the project parameter, but the schema covers the latter, making the overall description complete enough for its complexity.

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?

The input schema has 100% coverage for the single optional 'project' parameter, described as 'Optional project identifier.' The description does not add any further semantic detail for this parameter, so the baseline score of 3 applies.

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 uses a specific verb ('Get') and a resource ('context snapshot') that is clearly defined as a combination of summary, active blockers, and immediate pending tasks. This distinguishes it from sibling tools that focus on a single aspect, such as get_project_summary, find_blocked_tasks, or next_tasks, making its purpose unambiguous.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not name sibling tools, suggest scenarios, or state when not to use it. While the combined nature of the snapshot implies a high-level overview use case, the agent receives no direct steering toward or away from this tool.

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