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

Annotations already cover read-only, idempotent, and closed-world behavior, so the baseline is low. The description adds genuinely new context—dual consent requirements and owner-scoped data isolation—but says nothing about pagination behavior or what the 'field directory' projection actually does.

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?

Three short sentences, content front-loaded, and the consent/scope constraints are placed after the payload listing. Nothing is redundant, though the scope sentence could be merged more tightly with the consent sentence.

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?

With no output schema and a low-coverage input schema, the description should explain the field-directory projection and pagination model that the 'path' parameter implies. It covers the content and access model well but leaves the mechanics of retrieval entirely undocumented.

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 only 33%: 'path' is documented but 'limit' and 'offset' have no descriptions. The description does not compensate at all—it never mentions projection paths, page size, or offset semantics, so an agent must guess how to traverse a large context.

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?

Names a specific verb ('Read') and enumerates the returned content: watchlists, symbols, service access, and broker portfolio summary. It is largely distinguishable from siblings, though 'saved broker portfolio summary' overlaps conceptually with read_portfolio and the description does not clarify the boundary.

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 prerequisite ('Requires both Workspace and portfolio consent') is stated, which helps an agent decide whether it can run at all. However, there is no explicit guidance on when to use this versus read_workspace or read_portfolio, leaving the sibling routing to inference.

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