ecp_mssql_browse_rows

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It mentions that the tool connects with a specific db_username/password and that the user must be owned by the account, which is a useful auth requirement. However, it does not state that the operation is read-only, does not describe pagination behavior, filtering syntax, sorting defaults, or any side effects. This is minimal disclosure for a browsing 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 extremely concise: two sentences, no redundant text. The purpose is front-loaded in the first sentence, and the auth note is in the second. It avoids fluff and is easy to scan. However, the extreme brevity may border on under-specification, but as a standalone text it is efficient and well-structured.

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?

With 9 parameters, nested objects (filters), no output schema, and no annotations, this tool is moderately complex. The description barely scratches the surface—only a bare purpose and an auth requirement. It lacks essential context like how to construct filters, what pagination defaults are, whether sorting is allowed, what the response format looks like, or any limitations. This is severely incomplete for an agent to use the 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 schema description coverage is 0%, so the description must compensate by explaining the parameters, but it does not. It only references db_username and password implicitly, without detailing their requirements beyond the ownership note. The other parameters (db_name, table_name, page, page_size, filters, sort_column, sort_direction) are entirely undocumented in the description, leaving the agent to guess their semantics and relationships.

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 states the action clearly: 'Browse rows in a table.' This specifies a verb and resource, and the tool name 'ecp_mssql_browse_rows' further indicates the MSSQL context, distinguishing it from non-DB tools and write operations. However, it does not explicitly differentiate from sibling browse tools like ecp_mysql_browse_rows or ecp_postgres_browse_rows, though the name provides that distinction.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of conditions (e.g., database type, row size, read-only scenarios) that would lead an agent to select this over other browse tools or other operations. The only contextual note is about the required user ownership, which is a dependency, not a usage guideline.

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