basecamp_get_person

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The phrase 'Get details' implies a read operation, but it does not disclose what details are returned, whether any special permissions are required, or how errors are handled. This is insufficient for an unannotated tool.

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 short sentence, which is concise, but it omits essential information such as the required parameter and the nature of the returned data. While it is not verbose, it sacrifices clarity for brevity, making it only minimally effective.

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 has a simple structure (one parameter, no output schema), but the description still fails to note that 'person_id' is required or what kind of details are provided. With no annotations and no output schema, the agent has almost no context to invoke this tool correctly.

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?

The input schema defines only 'person_id' as a required string, but there is no description in the schema (0% coverage). The tool description does not mention 'person_id' at all, leaving the agent to guess the format or source of the ID. This is a complete lack of semantic guidance for the sole parameter.

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's function: 'Get details about a specific person.' It specifies a verb ('Get') and a resource ('details about a specific person'), which distinguishes it from list-oriented siblings like basecamp_list_people. The name and description align well.

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 guidance on when to use this tool versus alternatives. It does not mention that it is intended for fetching a single person by ID, nor does it contrast with list tools or explain prerequisites. No exclusions or alternative tool references are given.

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