get_context

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

With no annotations, the description carries the burden. It clearly communicates that this is a read-only aggregation via 'Get' and discloses the return content (active projects, blockers, decisions, etc.). It does not explicitly say 'does not modify state,' but the verb and return list make the behavioral profile sufficiently transparent.

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?

Three short sentences with no filler: what it returns, what content is included, and when to call it. The timing guidance is front-loaded after the purpose, and every sentence earns its place.

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 output schema, the description still enumerates the returned briefing categories. All parameters are optional and fully explained in the schema. For an aggregation/overview tool, everything an agent needs to call it appropriately is present.

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 100%, so the parameters (hours, project_id, include_completed) are fully documented in the schema. The description adds little parameter-specific meaning beyond 'recent activity,' matching the baseline for high schema coverage.

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 and resource: 'Get a structured briefing of the vault's current state.' It enumerates the contents of the briefing, making it clearly distinct from narrower sibling tools like get_project_status or list_tasks.

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?

Gives explicit when-to-use guidance: 'Call this FIRST in any new session to understand what's going on.' It does not mention when to avoid it or name alternatives, but the context is clear.

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