polarity_get_graph

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

The description uses 'Read', indicating a read-only operation with no side effects. While no annotations are present, the verb is clear. However, it does not explicitly state that it is safe or mention any permissions, which could be improved.

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 three sentences: purpose, parameter explanation, and usage guidance. Every sentence adds value, and there is no redundant information.

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?

The description covers purpose, parameter, and usage well. However, it lacks any mention of the output format or structure of the graph view, which would be helpful given there is no output schema.

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 only parameter ('entity') is fully explained with its three enum values and their meanings. This adds significant value beyond the schema, which only lists the enum without descriptions.

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 clearly states the verb 'Read' and the resource 'user's graph view,' and differentiates three projections ('user', 'cosmos', 'polarity'). This distinguishes it from sibling tools like 'polarity_ask' or 'polarity_dump'.

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?

Explicit guidance is provided for when to use each entity value: 'Use 'user' for general questions' and 'Use 'polarity' when comparing...', which helps the agent select the correct parameter value.

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