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

No annotations are provided, so the description carries the full behavioral burden, and it does describe the return shape (dimensions with score/max and evidence, grade, total /100). However, it discloses nothing about access requirements, behavior for an unknown slug, or any side effects, leaving the operational profile thin.

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?

A single dense sentence that front-loads the resource and enumerates the dimensions compactly. It is efficient, though the parenthetical list makes it slightly heavy 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?

Because there is no output schema, the description usefully explains the returned fields, and for a one-parameter read tool that covers most of the gap. Still missing are the meaning of the required slug argument and any routing guidance relative to sibling assessment tools.

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 the description never mentions the single 'slug' parameter at all, so an agent gets no explanation of what identifier is expected. With one undocumented parameter the description fails to compensate for the schema gap.

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 names the specific resource (a project's 6-dimension Freedom score) and enumerates the exact dimensions returned, so an agent knows precisely what this tool produces. It is clearly distinguishable from get_returns_breakdown and compare_projects by resource, though it never explicitly contrasts itself with them.

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 can infer you call this to fetch a project's freedom score, but there is no statement of when to prefer it over get_project_assessment or compare_projects, nor any prerequisites. No exclusions or alternatives are given.

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