Get shared team context

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

With no annotations, the description carries the burden of disclosing behavior. It transparently states that it fetches from .hub/, what content it returns, and that it pulls the latest from git first. It does not detail failure modes or explicitly label the operation as read-only, but the side effect of the git pull is disclosed, which is meaningful for a zero-parameter tool.

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?

Two sentences accomplish a lot: the first fronts the primary purpose and content, the second adds the git behavior and the sibling alternation. Every sentence earns its place, with no filler or repetition.

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 zero-parameter tool with no output schema and no annotations, the description covers the source, the data returned, the git-pull behavior, and the main alternative. It could go slightly further by noting the output shape or failure conditions, but the enumerated content gives an agent a solid mental model of what to expect.

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 tool has zero parameters and schema coverage is 100%, so there are no parameter semantics to explain. Per the rubric, a zero-parameter tool gets a baseline of 4; the description adds no misleading parameter information and focuses on behavior and output content.

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 ('Fetch') and resource (shared plan from .hub/ plus recent teammate activity), and enumerates the contained data: tasks with status/owner/declared interface. It also names the sibling alternative get_handoff_brief, making it easy for an agent to distinguish this tool from similar context-gathering tools.

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?

Explicitly tells the agent when to use a different tool: 'For picking up someone else's work, prefer get_handoff_brief instead', with a concrete reason (it includes richer handoff-specific context). This is clear routing guidance beyond a generic description.

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