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

With no annotations provided, the description carries the full burden. It discloses 'Approval restrictions apply to every call,' which is useful, but it does not state whether the tool is read-only, whether it has side effects, how query/offset affect results, or what happens when node_type and operation are null. The behavioral profile is incomplete.

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?

Two sentences with no fluff. The first sentence states the purpose, the second gives a parameter hint and a constraint. Everything earns its place and is front-loaded.

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?

Given 5 parameters and an output schema, the description is incomplete. It doesn't explain how to use query and offset, nor does it clarify whether the tool lists all operations or just fetches a schema for a specific one. The approval restriction is mentioned but not detailed. The output schema exists, so return values needn't be described, but correct invocation is underspecified.

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 description coverage is 0%, so the description must compensate. It explains node_type and operation (they are for fetching an argument schema) but leaves query, offset, and credential_id unexplained beyond the schema's types/defaults. The required credential_id is not semantically described, and query/offset are entirely ambiguous.

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 'Discovers a connection's operations without a workflow,' giving a specific verb and resource. It hints at differentiation from workflow-based tools but doesn't name a sibling explicitly. The phrase 'without a workflow' distinguishes it from operations tied to workflows, but it's not as crisp as naming the alternative.

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 some parameter usage guidance ('Pass node_type and operation for its argument schema') but does not state when to use this tool vs alternatives like search_operations or get_node_operations. No exclusions or conditions are provided, leaving the agent to infer when this is the right choice.

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