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

Goes well past readOnlyHint by disclosing auth/token scope requirements, that passkey approval and immediate posting are unavailable, that future scheduling needs drafts scope, and that the token's workspace is the default when omitted. These are real behavioral constraints an agent could not derive from the annotations.

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?

Dense and front-loaded, with every clause carrying a constraint; the semicolon-chained qualifiers make it slightly run-on but nothing is filler.

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 generic passthrough tool with a free-form nested arguments object and no output schema, it covers the key prerequisites and constraints. The main remaining gap is not indicating where valid operation_ids come from.

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 0%, so the description must compensate: it explains that operation_id selects the operation and that arguments must match that operation's full input schema, which is useful framing. However, it never says where to obtain an operation_id (e.g. via getOperation) nor gives argument examples, so the nested free-form object remains underspecified.

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?

States a specific verb and resource ("Executes a read-only API operation") plus the identifier used to select it, and explicitly says "Rejects write operations", which cleanly separates it from the callWriteOperation sibling.

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?

Gives a clear when-not (write operations are rejected, so route those elsewhere) and notes the prerequisite that the caller's token and scopes apply. It never names callWriteOperation explicitly, so the routing is inferred rather than spelled out.

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