wordpress_get_table_preview

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 the default of first 10 rows, which is useful, but does not cover critical aspects like read-only nature, potential permissions needed, error handling, or return format. This leaves significant gaps for a tool that likely involves database access.

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, efficient sentence that front-loads the core purpose ('Get preview of table data') and includes a useful detail ('first 10 rows by default'). There is no wasted text, making it appropriately concise 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?

Given the complexity of database table access, no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on behavior, parameters, return values, and error conditions, making it inadequate for safe and effective tool invocation by an AI agent.

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%, with one parameter 'table' undocumented in the schema. The description does not add any meaning about this parameter, such as what constitutes a valid table name or examples. It fails to compensate for the low schema coverage, leaving the parameter's semantics unclear.

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 ('Get preview') and resource ('table data'), specifying it retrieves the first 10 rows by default. However, it does not explicitly differentiate from sibling tools like 'wordpress_get_table_structure' or 'wordpress_list_tables', which might handle similar data but with different scopes or details.

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 such as 'wordpress_get_table_structure' for schema details or 'wordpress_execute_sql' for custom queries. The description implies a quick preview but lacks explicit context or exclusions for usage.

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