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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description's only added behavioral detail is 'privacy-filtered project metadata,' which hints at filtering but does not explain what is filtered, auth requirements, or response behavior.

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?

It is a single short sentence, but the phrasing 'Read hosted get ownership' is awkward and not front-loaded with a clear action+resource. The sentence does not earn its place because it fails to convey actionable meaning.

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, an agent needs the description to explain what ownership data is returned and how privacy filtering affects it. The description does none of this, and it adds no clarification for the three parameters despite malformed schema descriptions.

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 100%, so the baseline is 3. However, the schema descriptions for sessionId and executionId are erroneous copies of the projectId description, and the tool description does nothing to clarify any of the three parameters.

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 restates the tool name ('get ownership') and adds only a vague qualifier ('using privacy-filtered project metadata'), without defining what ownership is (project? user? code?) or distinguishing it from sibling getters like get_project_health or get_graph_scope. This is close to a tautology.

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 when-to-use guidance or alternatives are provided. It does not indicate when to call get_ownership versus list_linked_projects, map_project, or other get_* tools.

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