Coda MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'optional filtering' and implies a read operation, but fails to specify critical details like pagination behavior, rate limits, authentication requirements, or what happens when no rows match. For a list operation with potential large datasets, this is a significant gap in transparency.

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 at just 8 words, front-loading the core functionality ('List all rows in a table') and efficiently adding the key feature ('with optional filtering'). Every word serves a purpose with zero redundancy, making it easy for an agent to parse quickly.

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 complexity of a list operation with filtering capabilities, no annotations, and no output schema, the description is insufficient. It doesn't explain what the output looks like (e.g., row structure, pagination tokens), doesn't mention error conditions, and provides minimal behavioral context. For a tool with 4 parameters and sibling alternatives, this leaves too many gaps for reliable agent use.

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 input schema already documents all parameters thoroughly. The description adds minimal value by mentioning 'optional filtering' which corresponds to the 'query' parameter, but doesn't provide additional context about filter syntax or practical usage examples. This meets the baseline for high schema coverage.

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 action ('List all rows') and resource ('in a table'), making the purpose immediately understandable. It distinguishes from siblings like coda_create_row or coda_update_row by focusing on retrieval rather than modification. However, it doesn't explicitly differentiate from coda_get_table, which might also retrieve table data, leaving some ambiguity.

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 like coda_get_table or coda_list_columns, nor does it mention prerequisites such as needing a document ID and table ID. It lacks context about typical use cases or limitations, leaving the agent to infer usage from the tool name alone.

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