get_project

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

The readOnlyHint annotation already indicates a safe read operation, and the description's 'Get details' is consistent. It adds the 'Basecamp Classic' context but does not disclose error handling, return format, or any constraints beyond what the annotation implies. Adequate but not rich.

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 extremely concise, with two short lines and zero filler. The Args listing is structured and directly to the point.

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 simplicity (one ID parameter, read-only, output schema provided), the description is sufficient. It could have referenced list_projects as the alternative for retrieving all projects, but that is not essential for correct invocation.

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 has 0% description coverage, so the description must compensate, but it only says 'The numeric project ID', which largely restates the integer type. It does not explain where the ID comes from or any constraints, leaving the parameter under-explained.

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 'Get details for a specific Basecamp Classic project', using a specific verb and resource. This distinguishes it from list_projects (which lists all projects) and other 'get' sibling tools by focusing on a single project.

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?

Usage is implied: use this tool when you have a project_id and need details for one project. However, there is no explicit guidance on when not to use it or mention of alternatives like list_projects for fetching multiple projects.

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