Goals and decisions of my company

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

The description does add genuinely useful behavior not in the annotations: an empty organisation is created on first use, which is a state-changing bootstrap. That directly tensions with the declared readOnlyHint=true, so an agent relying on the annotation to call freely would be misled about side effects. The disclosure is honest, but the structured and prose signals conflict.

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?

Two sentences with the payload enumerated first and the provisioning caveat second, which is the right ordering. The trailing clause 'as its own app does on first visit' is illustrative but adds little for an agent.

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, the description carries the burden of describing the return value; it lists the content categories but not the shape or format (markdown block, JSON, single document), nor what an empty org returns. For a zero-param read this is adequate but incomplete.

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 schema has zero parameters, so there is nothing for the description to disambiguate; the 4 baseline applies. The description correctly implies the target is implicitly the authenticated person's organisation, not an arbitrary one.

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 verb+resource is clear and the returned content is enumerated ('goals, constraints, decisions and principles'), so an agent knows exactly what data this yields. It does not, however, distinguish itself from nearby siblings such as get_company, research_company, or get_project_context, leaving overlap resolution to the agent.

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?

There is no statement of when this tool should be called instead of get_company, research_company, or get_project_context. The agent must infer from the name alone that this is the context-loading call rather than the company-profile or research call.

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