get_project_context

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

With no annotations, the description carries the transparency burden. It discloses that the tool returns a full context note and lists contained data types, which is useful. It does not mention potential side effects, performance implications, or failure behavior, though the 'get' naming and 'Returns' wording imply a read-only operation.

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 short and front-loaded with a clear summary, followed by return details and an Args section. There is minor redundancy between 'metadata, sections, tasks, activity, and references' and the second sentence's list, but overall it is concise and easy to scan.

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?

For a low-complexity tool with one parameter and an output schema, the description provides enough information to invoke the tool correctly. It explains what kind of input is expected and what kind of output is returned, though it lacks explicit guidance on alternatives or edge cases.

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 coverage is 0%, so the description must compensate. It adds meaning beyond the bare string type by specifying that project_name can be either a name or an ID, which is sufficient guidance for this single-parameter tool.

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 opens with a specific verb and resource: 'Get rich context for a project,' and then enumerates the content areas (metadata, sections, tasks, activity, references). It also clarifies it returns the full context note including recent task activity, backlinks, and outgoing links, which differentiates it from more narrowly scoped siblings like get_metadata, find_backlinks, and find_outgoing_links.

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 usage: use this tool when you need broad, rich project context as opposed to a single facet. However, it does not explicitly state when not to use it or mention alternatives such as get_project_status, get_project_progress, or find_backlinks, leaving routing partly to inference.

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