get_project_context

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

Describes behavior as 'pure read' and explains return value (markdown string, empty string if no context). Without annotations, this is clear but could be more detailed (e.g., no side effects, idempotent).

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?

Very concise with structured sections (USE WHEN, NOT FOR, BEHAVIOR, PARAMETERS). No wasted words, front-loaded with main purpose.

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 output schema exists, description covers usage, return value, parameter guidance, and exclusion. No gaps for this simple 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?

Adds meaning beyond schema by specifying parameter format: 'project slug as returned by list_projects or get_active_project.' Schema coverage is 0%, so this is crucial and well done.

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?

Description clearly states it returns the full PROJECT_CONTEXT.md content for a specific project, using verb 'returns' and specifying the resource and scope. Distinguishes from sibling get_activity_summary.

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 provides 'USE WHEN' and 'NOT FOR' conditions, recommending an alternative tool (get_activity_summary) for live activity.

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