Profile Fields List

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description contributes genuinely new behavioral context — that all_pages is bounded and that every page consumes API quota — which is useful, though it is stated tersely and omits error/rate-limit behavior.

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?

It is short and the quota caveat is front-loaded, but the first clause merely repeats the tool title and 'Reads community data' is filler. Roughly half the text 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?

With no output schema and seven fully documented parameters, plus annotations covering safety, the main missing piece is usage routing (sibling disambiguation and when to set account/archived/all_pages). For a read-only list tool the schema carries most of the burden, but the description leaves the selection context uncovered.

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 100%, so the schema already documents all seven parameters including page, label, account, archived, all_pages and max_items. The description only echoes the all_pages/quota constraint and adds no parameter-level meaning beyond the schema, so the 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 opens by restating the title ('Profile Fields List') and then says only 'Reads community data', which is a generic tautology rather than a statement of what is listed or from where. It does not distinguish this tool from the sibling list_page_profile_fields, so an agent cannot tell which listing endpoint applies.

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?

There is no when-to-use guidance, no prerequisite (e.g., credential requirement for the 'account' parameter), and no mention of the sibling list_page_profile_fields as the alternative. Usage must be inferred entirely from the name and schema.

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