Get Schedule Import Processing State

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

While annotations indicate read-only and idempotent, the description introduces contradictory behavioral claims (pagination, record details) that are not aligned with the endpoint's processing status check. This misleads about what the tool actually does.

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 concise but structurally confusing due to mixed messages about the tool's function. It is not front-loaded with the core 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?

No output schema is provided, and the description's description of paginated record details is irrelevant to a processing status endpoint. The tool's actual response is not explained, making it very incomplete.

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%, and the description merely restates 'Required parameters: project_id' without adding new meaning. Baseline score of 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 description initially states it gets processing status, but then contradicts by saying it fetches full details of Schedule (Legacy) records and returns a paginated JSON array. This inconsistency obscures the tool's actual purpose.

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?

No guidance on when to use this tool versus alternatives. The mention of 'Schedule (Legacy)' is vague, and there is no distinction from other schedule-related tools.

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