Get the repo's handoff template

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the template may include required sections and instructions the agent must follow, which is genuinely useful behavioral context, but it is silent on failure modes (no repo, no template) and on whether the result should be re-read per session.

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 short sentences, no filler, with the resource definition first and the sequencing instruction second. Every clause carries information an agent needs.

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 parameters and no output schema, the description's job is to convey what comes back, and it does: extra sections, some required, plus sharing instructions. Only the edge cases (missing template, non-repo context) are unaddressed, which is minor for a zero-arg read tool.

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?

Zero parameters and 100% schema coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; the description's note that the template is scoped to 'the current repo' implicitly explains why no repo argument exists.

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 states a specific resource and scope: 'The handoff template for the current repo', plus what it contains (extra sections, some required, and sharing instructions). The name 'share_template' sounds like a write/sharing action, and the description corrects that, though it never uses a retrieval verb like 'returns' or 'fetches' so the read nature is only implied.

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?

'Call it before share_current_session' gives explicit sequencing guidance and names the relevant sibling. It stops short of saying when not to call it, whether a repo context is required, or what to do if no template exists.

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