spreadsheet_register

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

No annotations provided. Description explains extraction of ID from URL but does not mention persistence, idempotency, or error handling (e.g., duplicate registration). Moderate 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?

Two concise sentences, no redundancy, correctly front-loaded with purpose.

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 no output schema and low parameter complexity, description fully covers registration purpose, ID extraction, and parameter semantics. No gaps.

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% with descriptions. Description adds value by specifying 'alphanumeric ID from /oo/r/{id}' for spreadsheet_id and 'display name used to look up' for name, going beyond basic schema.

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 it 'registers a Synology Spreadsheet so it can be addressed by name', distinguishing it from siblings like spreadsheet_create (creates new files) and spreadsheet_list (lists existing).

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?

Description implies use when you have an existing spreadsheet ID and want to assign a name for later lookup, but lacks explicit when-not or alternatives (e.g., vs. spreadsheet_create). Context is clear but no exclusions.

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