get_project_context

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions 'bounded' and 'recent' but does not explain bounding behavior, ordering, filters, or side effects. It does not state whether the operation is read-only or if permissions are required. The description does not contradict any annotations, but it provides minimal behavioral context.

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, efficient sentence that front-loads the primary purpose. It avoids redundancy with the schema and annotations. However, it sacrifices necessary detail for brevity, so it is not a perfect 5.

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 the tool's complexity (3 parameters, output schema) and the existence of overlapping sibling tools, the description is too sparse. It does not explain what 'important Signals' means, how limits interact, or when to prefer this over get_signal_timeline. The output schema exists but the description still needs to set expectations for the combined result set, which it fails to do.

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 only 33% (only 'repository' has a description). The tool description adds no parameter-specific meaning, failing to link 'bounded important Signals' to signal_limit or 'recent Observation Events' to event_limit. The parameter names and schema defaults provide some semantics, but the description does not compensate for the 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?

The description clearly states the tool retrieves project metadata plus important signals and observation events, using the specific verb 'Get.' It identifies distinct resources (metadata, Signals, Observation Events) which helps distinguish it from generic 'get' tools. However, it does not explicitly differentiate from siblings like get_signal_timeline, which may overlap on Signal retrieval.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or comparisons with sibling tools such as get_signal_timeline or search_project_updates. The usage context is only implied by the tool's name and brief description.

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