spreadsheet_get_info

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

No annotations, so description must fully disclose behavior. States it returns metadata but doesn't explicitly declare it as read-only or safe. Simple get operation, no contradictions, but lacks explicit safety cues.

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, front-loaded with verb and resource, then specific output. No extraneous words.

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?

No output schema, but description explains what is returned: sheet names, row and column counts. Sufficient for a simple metadata tool. Could mention other possible metadata but acceptable.

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 coverage is 100%, baseline 3. Description adds value by clarifying that 'file_id' or 'name' should be provided (one of the two) and 'path' disambiguates. Provides practical usage guidance beyond property descriptions.

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?

Clear verb 'Get metadata' specifies the resource 'Synology Spreadsheet file' and includes concrete output 'sheet names, row and column counts'. Differentiates from sibling tools like spreadsheet_read_sheet (cell data) and spreadsheet_list (file list).

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?

Provides basic instruction 'Provide either file_id or name', but no explicit guidance on when to use this tool vs alternatives. Implied by purpose but not stated.

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