food_pending

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

No annotations are provided, so the description carries the full behavioral burden, yet it only signals that authentication is required. It does not disclose read-only vs mutating nature, return shape, pagination, or what happens with an invalid/expired token.

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?

It is admirably short and front-loads the resource, but it is a fragment rather than a structured sentence; the brevity here reflects under-specification rather than disciplined concision.

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 tool with an undocumented auth parameter, no annotations, and no output schema, the description does not supply enough for an agent to call it confidently or interpret the result. The login note is the only useful context provided.

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 single 'token' parameter has 0% schema description coverage, so the schema explains nothing. The description's '(needs login)' weakly implies the token is an auth credential, but offers no format, source (food_login_verify?), or expiry semantics.

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 phrase 'Pending food orders' identifies the resource but supplies no verb (list? fetch? confirm?) and does not distinguish itself from siblings like food_order_new or food_basket_create. An agent can guess it retrieves pending orders, but the operation type is inferred rather than stated.

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 only guidance is '(needs login)', which is a prerequisite rather than a when-to-use rule. Nothing tells the agent how this differs from food_order_new, food_basket_create, or food_detail, so selection among siblings is left entirely to inference.

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