wrike_get_account

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

No annotations are provided, so the description has the full burden of disclosing behavior. It only states a read operation, but does not mention response format, authentication requirements, rate limits, or how the 'fields' parameter affects results. It offers minimal insight beyond the tool name.

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?

The description is a single, clear sentence with no extraneous words, front-loading the verb and resource. While it is concise, it is arguably too terse to be fully useful, but it earns points for efficient structure.

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 tool with no annotations, no output schema, and only a vague parameter description, the description should provide more context about what account information is returned and how the optional 'fields' parameter works. The current description leaves these crucial aspects unexplained, making it incomplete for reliable tool selection and 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?

The input schema covers the single parameter with a description ('Additional fields'), achieving 100% schema coverage, so the baseline is 3. However, the description itself adds no extra meaning to the parameter, and the schema description is vague.

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 uses the specific verb 'get' and names the resource 'account information', which clearly identifies the tool's function. However, it lacks detail on the scope of account information, making it slightly generic compared to more explicit sibling descriptions.

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 provides no guidance on when to use this tool or how it differs from other getter tools in the sibling list. There is no mention of alternatives, prerequisites, or typical use cases.

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