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

Since no annotations are provided, the description carries the full behavioral burden. It clearly says the operation is read-only, never spends the user's quota, and returns rows newest first with id, created_at, and submitted data. This is solid coverage for a read-only tool.

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 three concise sentences, each earning its place: what the tool returns, when to use it, and how collection names map to the site. Key details are front-loaded and nothing is redundant.

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?

For a 4-parameter tool with no annotations and an output schema, the description gives enough context to safely invoke it: return shape, ordering, total count, collection naming, and quota behavior. The only real gap is how an agent would discover the exact project_guid and collection values, but the description provides enough for correct usage in most cases.

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?

The description adds real meaning beyond the schema by explaining that 'collection' refers to the data-collection values used in the site's forms. However, it does not directly clarify project_guid or how offset/limit interact beyond the newest-first ordering, so parameter guidance is incomplete.

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 opens with a specific verb and resource: 'Read what visitors submitted to one of this site's collections.' The concrete examples — bookings, leads, RSVPs, orders — remove ambiguity and clearly distinguish this from the sibling tools like create_database or build_site.

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?

It explicitly states when to use the tool: when the user asks what came in, who signed up, or wants a summary of submissions. It doesn't mention alternatives or exclusions, but the guidance is precise enough for an agent to route on.

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