basecamp_get_document

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only adds 'full content' as a detail about the return, but does not state whether the operation is read-only, what happens if the document is not found, or any side effects. This is minimal for a tool without annotation support.

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, front-loaded sentence with no redundancy. Every word earns its place, stating exactly what the tool does without unnecessary elaboration.

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 is simple with only two parameters and no output schema, so the description's limited detail is somewhat acceptable. However, the absence of parameter explanations and usage guidance makes it less than complete for an agent that may need to understand how to invoke it correctly in different contexts.

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 0% and the description adds no parameter context beyond the schema's property names. The two parameters (project_id, document_id) are self-explanatory from their names, but the description does not clarify their purpose, format, or relationships, leaving a gap that the schema does not fill.

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 a specific verb ('Get'), a resource ('document'), and a qualifier ('specific', 'full content'), making the tool's purpose unambiguous. It distinguishes from sibling tools like list_documents or create_document by emphasizing retrieval of a single document with full content.

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 implies usage through the phrase 'specific document with full content', suggesting it is for retrieving a single document rather than listing or creating documents. However, it does not explicitly mention alternatives or exclusionary conditions, so the guidance remains implied rather than explicit.

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