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

With no annotations, the description carries the burden and does it well: it discloses role-dependent visibility (owner additionally sees member emails, monthly caps/spend, open invites and the newest 50 charges), states explicit privacy exclusions ("never their links", "never what it was about"), discloses that only the newest 50 charges are returned, and confirms no cost. It does not explicitly say the call is read-only or side-effect free, relying on "Same as GET /v1/team" to imply it.

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?

Front-loads the resource and packs a large amount of decision-relevant detail (role-based fields, exclusions, 50-charge cap, cost) into three sentences without filler. Minor noise: the phrase "or team null" is cryptic, and the long parenthetical about charges is dense to parse.

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?

An output schema exists, so return-value explanation is optional, yet the description still tells the agent which fields appear for which role, which is exactly the context needed to interpret the response. The remaining gaps are the unaddressed api_key parameter and no stated behavior when the caller has no team.

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 0% and there is one parameter (api_key, optional, nullable) that the description never mentions. "Same as GET /v1/team" faintly implies key-based auth, but the description does not compensate for the schema gap as required when coverage is below 50%.

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?

Opens by naming the exact resource and scope ("Your team... its name, pool (credits), seats, each member's name and role"), and the uniform reads make it distinguishable from write-side siblings like create_team, invite_to_team and remove_team_member. It never names an alternative directly, so the differentiation is implicit rather than explicit.

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?

Usage is only implied: an agent infers "call this to inspect your team" from the field inventory. There is no statement of when to prefer this over siblings such as balance, usage, or list_keys, and no prerequisites or failure conditions (e.g. not being a member) are given. The "Free. Same as GET /v1/team" line does help an agent recognize the cheap, well-known read path.

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