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

The description adds useful behavioral context: ordering, contents, invoice statuses including 'since deleted', and a 'Pro' access note. However, the annotations provide no safety hints and readOnlyHint=false sits awkwardly with the read-only-sounding 'audit log', so the agent gets no explicit statement about side effects or error behavior.

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?

A single dense sentence front-loads the core purpose and then efficiently lists the returned fields and statuses. The trailing 'Pro.' is minimal but adds a real access constraint without padding.

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 one-parameter lookup tool with no output schema, the description covers the output fields, ordering, and status semantics. It does not mention pagination or limits, which may matter for an audit log, but the description is otherwise enough for an agent to invoke it correctly.

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 schema only defines an opaque required string 'id', and description coverage is 0%. The description compensates by explaining that the parameter is a schedule id and directs the agent to schedule_list to discover it. It stops short of giving format examples, but for one parameter this is sufficient.

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 identifies the tool as an audit log for one schedule id, enumerates the exact fields returned, and orders them oldest first. It also names schedule_list as the source of the id, which distinguishes it from sibling schedule tools without needing to inspect their schemas.

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 a concrete usage pointer: use schedule_list to find the id. It does not explicitly state when to prefer this over schedule_get or schedule_upcoming, but the audit-log framing and field list make the intended use clear.

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