cwp_account_metadata

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

No annotations are supplied, and 'Get' implies a read-only operation, which is the main behavioral signal. The description does not disclose auth requirements, whether fields vary by account type, or anything about the 'etc.' set of fields, so meaningful gaps remain for a tool with zero structured behavioral coverage.

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?

One tight sentence with the verb and resource front-loaded and no filler. Every word 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, the description should characterize what is returned, and it only gives a vague partial list capped by 'etc.'. It is adequate for a trivial one-parameter read but leaves the return contract and sibling differentiation 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 coverage is 100% and the single 'username' parameter is fully documented in the schema. The description's parenthetical lists return fields, not parameter meaning, so it adds essentially nothing about inputs beyond the schema baseline.

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 a specific verb ('Get') and resource ('metadata for a CWP account') and hints at returned fields (domain, email, status). However, it does not distinguish this from the nearby cwp_account_info sibling, which an agent could easily confuse it with.

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 guidance on when to use this versus cwp_account_info or cwp_account_list, nor any prerequisites. The agent must infer the choice 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.