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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds the default-quarter behavior, which is useful context—especially since the schema also documents it—but it doesn't describe rate limits, pagination behavior, or what 'complete' entails beyond the obvious. It adds some value but not rich behavioral context beyond the defaults.

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, front-loaded with the core action, and the default behavior is stated clearly without waste. Every sentence earns its place.

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 read-only retrieval tool with full parameter documentation and annotations covering safety and idempotency, the description is nearly complete. It could mention pagination or the nature of the 13F data, but nothing critical is missing for correct invocation.

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%, so all parameters are documented in the schema. The description reiterates the quarter default behavior, which is already in the schema's description for 'quarter'. It adds minimal meaning beyond the schema, so baseline 3 applies.

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 states a specific verb and resource: 'Complete 13F portfolio of one fund for one quarter.' An agent can tell this is a retrieval of a fund's holdings, distinct from siblings like institutional_list_holdings or institutional_get_sentiment. The scope is clear and exact.

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 implies you use this to get a fund's portfolio, and notes the default quarter behavior, but it doesn't explicitly state when to use this tool versus alternatives like institutional_list_holdings. There is no mention of prerequisites or exclusions, leaving the agent to infer.

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