get_entity_submission_status

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds context about returning a JSON snapshot and optional token-scoped read-back, but does not disclose additional behavioral traits (e.g., rate limits, cache behavior). This is adequate but not exceptional.

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 a single, front-loaded sentence of 15 words. It efficiently communicates the core purpose and a key optional parameter without redundancy.

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?

Despite having no output schema, the description only states it returns a 'JSON entity snapshot', lacking details about the snapshot's contents or status information. A more complete description would clarify what the snapshot includes and how it relates to submission status. This is minimally viable but could improve.

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?

Description adds meaning to both parameters: 'for a submitted entity_id' clarifies that entity_id must refer to a submission, compensating for its missing schema description. It also explains guest_access_token as optional and its purpose, which matches the schema description. Given 50% schema coverage, the description significantly augments semantic clarity.

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 clearly states it returns a 'JSON entity snapshot for a submitted entity_id', distinguishing it from siblings like list_entity_submissions (which lists submission IDs) and retrieve_entity_snapshot (which works on any entity). However, it could explicitly differentiate from retrieve_entity_snapshot.

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 implies usage for retrieving a submitted entity's snapshot, optionally with a token. It does not explicitly state when to use this tool versus alternatives like retrieve_entity_snapshot or list_entity_submissions, nor does it mention when not to use it.

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