get_project_context

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

No annotations are provided, so the description carries the full burden. It states 'Fetches,' which suggests a read operation, but it does not disclose what 'all context' includes, whether 'active decisions' has a specific format, whether output is large or paginated, or any side-effect profile. The behavior remains underspecified.

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 a single, tightly written sentence with no filler. The core action and target resource are front-loaded, and every word contributes to the meaning.

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 (one required parameter, no output schema), but the description leaves the return payload opaque and does not guide selection among numerous sibling context tools. An agent could invoke it, but it would not know what to expect back or when this tool is the appropriate choice.

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 0%, so the description must compensate for the undocumented parameter. It names 'project_name' implicitly via 'for a specific project' but adds no detail about format, examples, ambiguity, or what values are valid. The single parameter is self-explanatory by name, but the description does not enrich it.

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 uses a specific verb ('Fetches') and names a clear resource ('all context and active decisions for a specific project'). It is not a tautology and gives an agent a basic idea of the tool's scope, though it does not explicitly distinguish it from sibling context tools like company_context_compile or search_memory.

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 the tool is for retrieving project context, but it provides no explicit guidance on when to choose this tool over the many sibling context/memory tools, nor any exclusions or alternative routing. An agent is left to infer usage from the name and minimal description.

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