Every Number

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

Annotations declare a non-read-only, open-world, non-idempotent, non-destructive operation, and the description adds substantial context beyond them: no AI reads the file, fixed layout rules and a database compute every number, the dashboard is public to anyone with the link and expires 24 hours after upload unless saved. It also discloses rate limits of 5 files per 10 minutes and 20 per day, which annotations cannot express.

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 core purpose and the return value are front-loaded, and most sentences carry real information (retention, rate limits, privacy). It is a dense single paragraph, however, and the input-path details in the middle overlap with what the schema already documents, so a small amount of text does not earn its place.

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 an output schema present the description need not explain return values, yet it still summarizes the receipt structure usefully. Annotations, full schema coverage, and the described retention, limits and access model together leave no material gap for an agent deciding how to call this tool.

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 100%, so the schema already documents file_url, file_content, content_encoding, sheet and file_name in detail. The description restates the file_url sources and the file_content/file_name pairing rather than adding new meaning such as precedence when both are supplied or how the nested 'file' object interacts with the top-level fields. Baseline 3 is appropriate.

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 first sentence states a specific verb and resource pair: turn an Excel/CSV spreadsheet into an Every Number dashboard, with the size ceiling included. It also names the concrete artifact produced (a read-only dashboard link plus every number with its receipt), so an agent knows exactly what comes back. No sibling tools exist, so no differentiation is required.

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?

The description gives explicit input-path guidance: use file_url for a Google Sheet shared as 'Anyone with the link', a Dropbox link, or a public GitHub file, or use file_content with file_name for raw CSV/base64. It also states 'No account needed' and the retention rule, which sets expectations for when this tool is appropriate. It stops short of stating when NOT to use it, but with no siblings there is little to exclude.

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