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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds only the raw endpoint mapping; it says nothing about result size, pagination behavior, sorting defaults beyond what the schema documents, or what a portfolio record contains.

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 short sentences, front-loaded with the purpose and the clarifying synonym. No filler, though the endpoint reference is marginally useful to an agent versus behavioral detail that could occupy the same space.

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 simple read-only list tool with fully documented parameters and safety annotations, this is barely adequate; there is no output schema, so a hint about what a portfolio includes (fields, count/ordering) would round it out.

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?

All four parameters are fully documented in the schema (100% coverage), including defaults and max page size, so the description needn't restate them. Baseline 3 applies since the schema carries the semantic load.

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 the verb and resource ("List portfolios") and adds a clarifying synonym "(property groups)" plus the backing endpoint GET /property-groups. That distinguishes it reasonably from doorloop_list_properties, though the description doesn't explicitly say how portfolios differ from properties as a domain concept.

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?

No statement of when to use this versus doorloop_list_properties or the other list tools, and no mention of pagination strategy or when to page through results. The agent must infer purpose from the name alone.

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