Returns Avatar Of The Current User

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

Annotations declare readOnlyHint=true, which matches the read nature. However, the description misrepresents the tool's function (avatar vs company settings). It adds pagination details but contradicts the primary purpose, reducing transparency.

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 cluttered with contradictory statements (avatar vs company settings). It includes unnecessary API reference details but fails to clearly state what the tool does. Not concise.

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?

No output schema, so description should explain return format. It mentions 'paginated JSON array of Company Settings' but this conflicts with the avatar purpose. Missing details on avatar data structure.

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% with good parameter descriptions. The description adds context about pagination (page, per_page) and required company_id, but adds little beyond the schema.

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 states 'Returns avatar of the current user' but then contradicts by saying 'Use this to read information about Company Settings... Returns a paginated JSON array of Company Settings.' This inconsistency severely undermines clarity. The endpoint suggests avatar retrieval, not company settings.

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 explicit guidance on when to use this tool vs alternatives. It says 'use this to read information about Company Settings' which is likely incorrect. No exclusions or context for decision-making.

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