BugSnag: Get Current Project

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

Annotations already mark the tool read-only and idempotent. The description adds valuable context beyond those annotations: the tool allows other BugSnag tools to be called without projectId, and the distinction between returning a project vs. returning nothing changes how subsequent tools must be invoked.

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 front-loaded with the core purpose and then organized into Toolset, Parameters, Use Cases, and Hints. It is longer than strictly necessary, but each section earns its place by helping an agent decide when and how to use the tool.

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 parameterless tool with comprehensive hover annotations and no output schema, the description fully covers what the agent needs: what the tool does, what return scenarios mean, and what alternative to call if no current project is set. Nothing important is missing.

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?

With zero parameters and 100% schema description coverage, there is nothing for the description to add about parameter meaning. The description confirms 'Parameters: None' and focuses on behavioral context, which is appropriate.

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 states a specific verb and resource: 'Retrieve the current project on which tools should operate by default.' It clearly distinguishes this from the sibling bugsnag_list_projects by focusing on the 'current' default project rather than all accessible projects.

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 Use Cases and Hints sections give explicit guidance: call this to understand whether a current project has been set, expect other BugSnag tools to use that project if one is returned, and fall back to listing projects if none is returned. It also explains when an explicit project ID will be required instead.

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