format_project_context_for_llm

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

No annotations provided, so description solely responsible. It discloses truncation with ellipsis when budgetChars is provided, but does not mention read-only behavior, side effects, or what happens when budgetChars is absent. Version string adds no behavioral info.

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?

Single sentence plus version tag, front-loaded with purpose and key behavior. No extraneous information. Highly efficient.

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?

Adequate for a simple formatting tool with only two parameters. Lacks details on return type (presumably a string), absence of output schema, and no mention of safety or side effects. Missing some behavioral context but covers the core use.

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 50%: budgetChars has a description, projectId does not. Description adds context for projectId ('ProjectContextRecord') but does not elaborate on format or constraints beyond schema. Compensates partially but not fully for low 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?

Description uses specific verb 'Render' and resource 'ProjectContextRecord', states target audience ('wakeUp L0 layer or system prompt'), and mentions truncation behavior. Distinguishes from sibling 'format_with_salience_budget' by specifying the use case (wakeUp L0 layer).

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?

Implied usage: for formatting context as a prose summary with a character budget. However, no explicit when-to-use or when-not-to-use guidance versus alternatives like 'format_with_salience_budget' or other formatting tools. Lacks exclusion criteria.

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