spreadsheet.rows

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

Mentions pagination and derivation from geometry attributes, which are key behaviors. However, with no annotations, the description fails to disclose default values, error conditions, or whether the operation is read-only.

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?

Single sentence is concise and front-loaded with the main action. However, it could include a brief example or clarification without becoming verbose.

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 4 parameters, no annotations, no output schema, and no parameter descriptions, the description omits critical context such as return format, pagination behavior, default values for object and component, and error handling.

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 does not explain any parameter beyond what the schema title provides. Terms like 'paginated' hint at limit/offset but lack specifics on how object and component affect results.

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?

Description clearly states verb 'Return', resource 'spreadsheet rows', and unique qualifier 'derived from object geometry attributes'. Distinguishes from sibling 'spreadsheet.columns' and 'spreadsheet.report' by specifying the data source and pagination.

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 on when to use this tool versus other spreadsheet tools or alternatives. Does not specify prerequisites, such as requiring an active object or geometry selection.

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