get_project_context

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

With no annotations, the description carries the burden of disclosing behavioral traits. It clearly describes the output contents, which is useful, but it does not mention that this is a read-only operation (though 'Get' implies safety) or potential performance/large-response considerations. Not misleading, but incomplete.

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?

The description is two concise sentences with no redundancy. It front-loads the primary purpose ('Get aggregated project context') and then provides a compact list of returned elements. Every word 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?

The tool is simple with no parameters, and the description succinctly summarizes the scope and return types. An output schema exists, so detailed return values are documented elsewhere. It does not mention potential data size or aggregation specifics, but this is acceptable given the low complexity.

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, so the baseline score of 4 applies. The schema coverage is trivially 100% and there is no parameter information to add, so the description does not need to compensate.

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 clearly states the tool's function with a specific verb ('Get') and resource ('aggregated project context'), and enumerates the returned content (sources, knowledge entries, rules, counts) from both catalog and review-extracted knowledge. This distinguishes it from sibling tools like get_domain_knowledge by emphasizing aggregation.

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?

The description implies when to use the tool (when aggregated project context is needed) but does not explicitly contrast it with alternatives or provide exclusions. It lacks direct guidance such as 'use this instead of X' but the aggregated scope makes the use case reasonably clear.

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