basecamp_index_find_column

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

No annotations are provided, so the description must carry the full behavioral disclosure. It only mentions 'fast lookup' without clarifying read-only nature, error handling if no match is found, or the fuzzy match semantics (which appear only in the schema). There is no mention of side effects or return format.

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?

A single well-structured sentence that is front-loaded with the verb 'find'. It is concise and contains no unnecessary words.

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 simple two-parameter lookup with no output schema, the description conveys the essential purpose. However, it omits behavior on no match and the expected return value. With no annotations, it is minimally adequate but leaves some gaps.

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 100%, so the schema already documents both parameters. The tool description does not add new meaning beyond the schema, but the schema's 'fuzzy match' note for column_name provides useful detail. Baseline of 3 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 uses a specific verb 'find', identifies the resource 'column', and scopes it 'within a project'. It also adds 'fast lookup' which distinguishes it from siblings like basecamp_list_columns and basecamp_get_column, making the tool's purpose unmistakable.

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 by the description: find a column by name. However, there is no explicit guidance on when to choose this over alternatives like basecamp_get_column (likely by ID) or basecamp_list_columns (all columns). No exclusions or alternative recommendations are provided.

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